id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc	phab_field
2469	link failure without not-used Boost.Signals library when Boost.Signals2 is used	fabio		"Since r13716 with Boost >= 1.54 Boost.Signal2 is used rather than Boost.Signal. However it still try to link to Boost.Signal and, if this is not available, linking fails:

{{{
/usr/bin/ld: impossibile trovare -lboost_signals
collect2: error: ld returned 1 exit status
make[1]: *** [../../../binaries/system/libAtlasUI.so] Errore 1
make: *** [AtlasUI] Errore 2
}}}

Removing:
{{{
unix_names = { os.findlib(""boost_signals-mt"") and ""boost_signals-mt"" or ""boost_signals"" },
}}}
from [http://trac.wildfiregames.com/browser/ps/trunk/build/premake/extern_libs4.lua build/premake/extern_libs4.lua] fixes it (there is no need to add other libs to link, since signals2 is apparently in main boost lib now).

Possible solutions:
* change the check to use signals2 from 1.54 and use 1.39 ([http://www.boost.org/doc/libs/1_55_0/doc/html/signals2/api_changes.html the first version with signals2], [http://www.boost.org/users/history/version_1_39_0.html released in 2009]), and remove all the signal link flags from extern_libs4.lua. We'll drop support for older boost version;
* just modify extern_libs4.lua to not use the signals link flags whit boost >= 1.54.

I would prefer the first approach, it simpler (remove some code from extern_libs4.lua) and not dependent on the Boost version."	defect	new	Must Have	Alpha 16	Build & Packages