2824 has a dependence on libgconf2-dev

[Jon-Olov Vatn]

Just a comment, when installing with "./boostrap; ./configure; make ;
make install" instead of using the build script, things went fine for me.
I also used revision 2824 with no gconf.

BW J-O

Cesc wrote:

> yes, u r right ... at least for non-critical parts like gconf, which
> we can very well use the always reliable xml-conf ... :)
>
>
> On 10/13/06, Gerald Maguire <maguire at it.kth.se> wrote:
>
>>     i guess it is a configuration issue ... you can disable gconf via
>> the
>>     build/build.conf.local config file ...
>>
>>     Cesc
>>
>> My assumption would be that if a libary is _not_ present, then the
>> configuration process should automatically disable it, rather than
>> breaking with an error about it not being present.
>>
>> Chip
>>
>>     On 10/12/06, Gerald Maguire <maguire at it.kth.se> wrote:
>>     > svn co svn://svn.minisip.org/minisip/trunk
>>     > ...
>>     > Checked out revision 2824.
>>     >
>>     > To compile libminisip required adding the "GConf development
>> libraries", which were loaded via:
>>     >   apt-get install libgconf2-dev
>>     >
>>     > This dependence should be noted on
>> http://www.minisip.org/develop_build.html
>>     >   in the section "Install the development package for the
>> external dependencies"
>>     > _______________________________________________
>>     > Minisip-devel mailing list
>>     > Minisip-devel at minisip.org
>>     > http://lists.minisip.org/mailman/listinfo/minisip-devel
>>     >
>> _______________________________________________
>> Minisip-devel mailing list
>> Minisip-devel at minisip.org
>> http://lists.minisip.org/mailman/listinfo/minisip-devel
>>
> _______________________________________________
> Minisip-devel mailing list
> Minisip-devel at minisip.org
> http://lists.minisip.org/mailman/listinfo/minisip-devel