Ignore:
Timestamp:
2010-12-07T23:41:49Z (14 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
76c89dc7
Parents:
83f1bd1d
Message:

At least don't disable Twitter anymore for libpurple builds. libpurple
doesn't have Twitter support by default and it's unlikely that someone will
prefer libpurple-twitter over BitlBee's Twitter code anyway.

Also automatically disable libpurple protocol modules if a native variant is
already set up. The linking conflict works the other way around (libpurple
modules may break if native modules for the same protocol are compiled in)
so this should mostly resolve the linking conflict problem.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • protocols/purple/purple.c

    r83f1bd1d rc775a58  
    12871287                struct prpl *ret;
    12881288               
     1289                /* If we already have this one (as a native module), don't
     1290                   add a libpurple duplicate. */
     1291                if( find_protocol( prot->info->id ) )
     1292                        continue;
     1293               
    12891294                ret = g_memdup( &funcs, sizeof( funcs ) );
    12901295                ret->name = ret->data = prot->info->id;
Note: See TracChangeset for help on using the changeset viewer.