boost installer - what should be expected
Hello, yesterday I downloaded the boost installer package from boost-consulting site (http://www.boost-consulting.com/download.html) and started the installation. Everything was fine, but now I have a question: After choosing and installing the desired libraries I would like to know what should be expected as a result? I selected to install the libraries for Visual C++ 8.0, but I still had to put manually into C++ Options Dialog the directories to boost includes, libs and binaries. Shouldn't this be done by setup? Would not it be better to create merge modules, so that boost users could use them for their installations as well? With Kind Regards, Ovanes Markarian
"Ovanes Markarian"
Hello,
yesterday I downloaded the boost installer package from boost-consulting site (http://www.boost-consulting.com/download.html) and started the installation. Everything was fine, but now I have a question: After choosing and installing the desired libraries I would like to know what should be expected as a result?
I selected to install the libraries for Visual C++ 8.0, but I still had to put manually into C++
Options Dialog the directories to boost includes, libs and binaries. Shouldn't this be done by setup?
I'm not sure if there's a way to do that, and even then, would it really be appropriate to force those settings on all of a user's projects?
Would not it be better to create merge modules, so that boost users could use them for their installations as well?
Sorry, what's a merge module?... Googling... oh, nice idea. Unfortunately it's not supported by the installer technology we chose AFAICT. -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
I selected to install the libraries for Visual C++ 8.0, but I still had to put manually into C++ Options Dialog the directories to boost includes, libs and binaries. Shouldn't this be done by setup?
I'm not sure if there's a way to do that, and even then, would it really be appropriate to force those settings on all of a user's projects?
These settings are not per-project in VS, at least not typically (I'm not sure whether per-project include paths are even possible). Neither do they hurt, in particular not with Boost, where all headers are in a subdirectory. On the other hand, you _have_ to add the include and library paths, or else hard-code the full path to the Boost includes in the include file names. Nobody does that. Sebastian Redl
Sebastian Redl wrote:
David Abrahams wrote:
I selected to install the libraries for Visual C++ 8.0, but I still had to put manually into C++ Options Dialog the directories to boost includes, libs and binaries. Shouldn't this be done by setup?
I'm not sure if there's a way to do that, and even then, would it really be appropriate to force those settings on all of a user's projects?
These settings are not per-project in VS, at least not typically (I'm not sure whether per-project include paths are even possible).
Yes, you can set both paths in Project/Properties... C/C++ -> Additional Include Directories Linker -> Additional Library Directories
Neither do they hurt, in particular not with Boost, where all headers are in a subdirectory. On the other hand, you _have_ to add the include and library paths, or else hard-code the full path to the Boost includes in the include file names. Nobody does that.
Well, they can hurt, when using cretain tools (i.e.: Visual Assist) those header which are set under Tools/options are considered "stable" and they are less frequently scanned/parsed for changes I think it should be an option in the installer, if that isn't too much trouble. It would be nice to set some enviroment variable like BOOST_INSTALLDIR in the installer so you could do: $(BOOST_INSTALLDIR)/libs or $(BOOST_INSTALLDIR)/include in Project/Properties , and be done with it. This will allow different people working in the same project to use the same project files even if they install boost to a different directory. ------------------------------------------------------------------------------------------------------------------- Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, contiene información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. Queda prohibida su divulgación, copia o distribución a terceros sin la previa autorización escrita de Indra. En el caso de haber recibido este correo electrónico por error, se ruega notificar inmediatamente esta circunstancia mediante reenvío a la dirección electrónica del remitente. POR FAVOR, ANTES DE IMPRIMIR ESTE CORREO ELECTRÓNICO CONSIDERE SU APORTACIÓN A LA CONSERVACIÓN DEL MEDIO AMBIENTE POR LA REDUCCIÓN DE CONSUMO DE PAPEL. The information in this e-mail and in any attachments is confidential and solely for the attention and use of the named addressee(s). You are hereby notified that any dissemination, distribution or copy of this communication is prohibited without the prior written consent of Indra. If you have received this communication in error, please, notify the sender by reply e-mail. PLEASE CONSIDER YOUR ENVIRONMENTAL RESPONSIBILITY BEFORE PRINTING THIS E-MAIL.
On 5/30/06, Sebastian Redl
These settings are not per-project in VS, at least not typically (I'm not sure whether per-project include paths are even possible). Neither do they hurt, in particular not with Boost, where all headers are in a subdirectory. On the other hand, you _have_ to add the include and library paths, or else hard-code the full path to the Boost includes in the include file names. Nobody does that.
Sebastian Redl
There are per-project include paths in VC++ - they're under the property 'Additional Include Directories' and are added using the -I option of cl. That's the mechanism by which I add third-party library paths to VC++ projects - although not hardcoded - I define a whole load of environment variables. I'm using VC7.1 - I use Solution Build Environment add-in (http://www.workspacewhiz.com/OtherAddins.html#SolutionBuildEnvironment) to define them, but in VC8.0 there is a built in mechanism (define a property sheet using the property manger, define the environment variables in the User Macros option) that can be used for that purpose. Why prefer per-project settings, I hear you cry? Well, for older projects that used older versions of Boost that I really don't want to upgrade! The last time I did that (1.30.0 to 1.32.0, I think), upgrading my use of the Boost.Iterator libraries was a bit of a pain. Oh yeah - there's also per-project library path settings as well - they obviously need to be set for Boost libraries needing linking. Stuart Dootson
participants (6)
-
David Abrahams -
Miguel Angel Lopez Font -
Olaf van der Spek -
Ovanes Markarian -
Sebastian Redl -
Stuart Dootson