Will the option “–address-model=32,64” build both 32 and 64 libraries or do you have to do two separate builds?
Will the option –address-model=32,64 build both 32 and 64 libraries or do you have
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Will the option “–address-model=32,64” build both 32 and 64 libraries or do you have to do two separate builds?
Doing:
Or..
Work and produces, depending on toolset and platform support, both 32 and 64 bit targets in the first case. And 32, 64, and 32+64 universal targets (most likely only on OSX using the
darwintoolset. And by “works” I mean that I just tried it with my Boost library on OSX with thedarwintoolset. Hence I suspect you have your syntax wrong, i.e. don’t use “–name=values” as they are not options, but instead use “name=values” are the are requirement specifications.