Subject: Re: [Boost-build] Missing libs?
From: Robert (r.firl_at_[hidden])
Date: 2017-11-15 17:11:54
On 11/15/2017 11:05 AM, David Bergman via Boost-build wrote:
> Thanks for the help.Â Though I will say that the Visual Studio Project
> Property Pages | Linker |
> General | Additional Library Directories property is actually set to the
> lib directory.Â I may have the dir name wrong and will check that.
> I will also look into your second comment.Â This is a little beyond my
> level of sophistication.
> In the event that these issues do not resolve I wonder if there could be
> a conflict with another "include" dir.Â For example, I want to use the
> traditional boost header files for math functions and have that path set
> in ... | VC++ Directories | Include Directories.Â Also, since I'm trying
> to use gp-io with this might there be a conflict with that?
I am not aware of a conflict. I have not directly used gp-io though. I
think if there is a conflict, you would observe duplicate or ambiguous
symbol messages from the linker.
> *From:* Robert via Boost-build <boost-build_at_[hidden]>
> *To:* boost-build_at_[hidden]
> *Cc:* Robert <r.firl_at_[hidden]>
> *Sent:* Wednesday, November 15, 2017 10:35 AM
> *Subject:* Re: [Boost-build] Missing libs?
> On 11/15/2017 8:38 AM, David Bergman via Boost-build wrote:
> > I recently posted about getting the boost libraries to build.Â This
> > issue is solved but I've run into another.
> > I'm trying to use gnuplot, and gnuplot-iostream to develop a GUI for
> > simulation s/w and the gp-iostream uses boost::iostream.
> > A simple example pulled form the gp-io site gives link errors, 7
> > unresolved externals.Â An example of one is,
> > error LNK2019: unresolved external symbol "public: void __thiscall
> > boost::iostreams::file_descriptor::close(void)"
> > (?close_at_file_descriptor
> <mailto:iostreams_at_boost>@@QAEXXZ) referenced in function
> > "public: static void __cdecl boost::iostreams::detail::close_impl<struct
> > boost::iostreams::closable_tag>::close<class
> > boost::iostreams::file_descriptor_sink>(class
> > boost::iostreams::file_descriptor_sink &,int)"
> > (??$close_at_Vfile_descriptor_sink
> <mailto:SAXAAVfile_descriptor_sink_at_23>@H_at_Z <mailto:H_at_Z>)
> > In the past with other libraries, similar errors were fixable (ensuring
> > correct path is set in the IDE, #includes are in correct order, etc).
> > I'm using VS 2017 and the "intellisense" isn't showing any issues.Â I
> > have added paths for includes and linker libraries the same way I've
> > done in the past with other libs and they've worked.
> > I'm reaching out to the boost community to see if anyone has had this
> > issue with a similar combination of libraries.
> It looks like the Visual Studio Project Property Pages | Linker |
> General | Additional Library Directories property is not set.Â If you
> are building for both 32-bit and 64-bit versions, you will have to have
> different paths to the Boost library files.Â There is not yet a bit size
> in the library file names.Â For example, on my various projects, I have
> all 32-bit library files in C:\Boost\lib.Â I have all 64-bit library
> files in C:\Boost\lib\x64.Â When the Visual Studio project's 32-bit
> Additional Library Directories property is user set, the ending string
> has a special automatically added value:
> Keep in mind that the Visual Studio Property Pages dialog drop down
> combination selection is key to knowing which configuration combination
> is modified.Â The dialog combo boxes do not synchronize with the current
> selection in the editing environment.
> > Thanks in advance for your help.
> > David
> > _______________________________________________
> > Unsubscribe & other changes:
> Unsubscribe & other changes:
> Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk