New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better custom compilation flags handling #717
Comments
[kiorky] I ll post a new patch a soon as the compilation pass but when i set custom ldflags, it just fails with an undefined symbol. Strangely "src" isnt anymore in LIBPATH, so the patch i will post add src in the LDFLAGS explicitly {{{ |
[kiorky] Uhm, no the problem was more compicated, i compile mapnik for another project and the policy in to put things in say "prefix", and we have a tool that add "-L/prefix -Wl,-rpath -Wl,/prefix" in the environment. Now, problem was i have a previous installed version of libmapnik in that /prefix and at compilation time "/prefix" took precedence on "src", so the upcoming patch i ll post take that in account. |
[springmeyer] thanks for the patch. ya, your first problem sounds like a config issue not a mapnik/scons issue. Overall CUSTOM_LD/CXX flags are set per target and not used globally. This surely is a problem if you try to use them to locate boost. BOOST_INCLUDES/BOOST_LIBS would be the recommended way to locate boost. |
[kiorky] The problem is there for other libraries than boost, just install something in a non standart place and cry. Useless to repeat that build tools (like mine) will set automaticly cflags & ldflags. |
closing, not actionable. |
Along side is a patch for custom cflags/ldflags handling.
Actually (without) it just doesn't take my flags in account (CUSTOM_CXX/LDFLAGS)
Also, it will modify the boost finder to search on those CFLAGS/LDFLAGS for custom directories.
The text was updated successfully, but these errors were encountered: