On Tue, 2009-04-14 at 20:47 -0400, Dale Worley wrote: > In rev. 15184 on the mainline I have updated how autoconf deals with > FreeSWITCH. Formerly, it just assumed that FS was installed > at /usr/local/freeswitch, without doing any checking. This could cause > difficult-to-diagnose failures at sipX start time. The revision creates > a CHECK_FREESWITCH macro very much like the CHECK_* autoconf macros that > locate and configure other third-party libraries.
> In particular, executing ./configure for sipXconfig or sipXfreeswitch > (the two components that need to know where FS is located) will halt > with an error if FS cannot be located. The only location that is > automatically searched is /usr/local/freeswitch, which is the location > where our sipx-freeswitch RPM installs FS. If FS is installed in > another location, that can be given in the --with-freeswitch=PATH option > for ./configure. Note that bin/freeswitch must exist in the given path, > and there is no provision for installing different parts of FS in > separate directories -- the alternative location must use the same > relative locations for the FS components as does the sipx-freeswitch > RPM This isn't really correct, I think. Having freeswitch installed is not a build-time dependency - it's a run-time dependency. This test caused some build failures last night because freeswitch is not on the build servers, but it's not really needed for the build. I think that test should be moved to a configuration test that's run by whatever needs it at 'configtest' time. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
