I've post this issue 3weeks ago,
And I now post it again.
I use 3rd party library in my project.
Boost C++ Library.
only circular_buffer.hpp header file make trouble.
I don't know what means error message.
so, I post error logs today.
===================environment
My mac os 10.11 version
Xcode version 7.1.1(7B1005)
C++ Language Dialect : c++11[-std=c++11]
C++ Standard Library : libc++(LLVM C++ standard library with C++11 support)
====================error logs
/Users/genosyde/Downloads/Coding/ofFrameWork/of_v0.9.4_osx_release/addons/ofxOSXBoost-master/libs/boost/include/boost/circular_buffer.hpp:39:27: No member named 'remove_pointer' in namespace 'boost::move_detail'
/Users/genosyde/Downloads/Coding/ofFrameWork/of_v0.9.4_osx_release/addons/ofxOSXBoost-master/libs/boost/include/boost/circular_buffer.hpp:40:27: No member named 'add_pointer' in namespace 'boost::move_detail'
/Users/genosyde/Downloads/Coding/ofFrameWork/of_v0.9.4_osx_release/addons/ofxOSXBoost-master/libs/boost/include/boost/circular_buffer.hpp:45:7: No member named 'disable_if_c' in namespace 'boost::move_detail'; did you mean '::boost::disable_if_c'?
/Users/genosyde/Downloads/Coding/ofFrameWork/of_v0.9.4_osx_release/addons/ofxOSXBoost-master/libs/boost/include/boost/circular_buffer.hpp:50:27: No member named 'is_const' in namespace 'boost::move_detail'
there are hundred of errors below.
thanks for reading and have a good day!!!
Thank you for your interest.
I'm sorry
But, I don't understand your request.
circular_buffer.hpp is 3rt_party library from boost.org.
Any time, you can download it for individual OS.
And I send you a link, that is my test project file link in google drive.
If you download it, you might just run it.
https://drive.google.com/open?id=0B4J46iW2HRnoYmNhcVB2OXhkX1U
my test of xcode porject's location:
of_v0.9.4_osx_release/addons/ofDelayLine/BoostTest/boostTest.xcodeproj
If you got Xcode, just double click it on finder.
I just add circular_buffer.hpp on ofApp.h to use it.
Related
I am trying to install SFML(2.5.1) in CODEBLOCK(20.03) with and currently using windows 8.1. I have downloaded sfml-tdm-sjlj-32 bit as per the tutorials that I saw in the web. I did all the set-ups and declared all the linkers properly but unfortunately it gave me error asking for libgcc_s_sjlj-1.dll not found so I downloaded it and added to my CODEBLOCK environment. After doing so I build and debugged a code that I got from SFML::CODEBLOCK tutorial just to test it but it gives me the following error -
The procedure entry point_gxx_personality_sj0 could not be located in the dynamic link library c:\sfm\sfml\sfm-graphics-d-2.dll
thank you in advance :)
Don't mix gcc exception models. Your environment probably uses Dwarf and now you want to use a library compiled with a GCC that uses SJLJ. Even if you get it to link it's likely to crash if there is any C++ code in there. Best is to use SFML compiled with the same compiler the rest of your environment uses, or even build it from source.
I'm having trouble linking an Xcode project using the AAF SDK, with Xcode 5.1.1 on MacOS 10.9.5. When I link the main dynamic library, these symbols come up missing:
_StgCreateDocfile
_StgCreateDocfileOnILockBytes
_StgOpenStorage
_StgOpenStorageOnILockBytes
AssertProc
I can't find a definition for them anywhere in the entire source tree for the SDK. The first four appear to be part of Structured Storage on Windows. A Structured Storage library is provided in the SDK and I'm already linking that.
Can anyone tell me of a Mac system library that defines these? Or is there a linker argument that pulls in a library for them? Thanks for any help.
A late answer (!), but in case anyone comes across this... The solution is either:
To use the makefiles with the AAF SDK to generate the AAF dylib,
which works fine. or...
If you use Xcode to build the AAF SDK, ensure the correct
#defines are kept, namely:
_DEBUG OM_DEBUG OM_STACK_TRACE_ON_ASSERT OM_USE_SCHEMASOFT_SS OM_STRUCTURED_STORAGE
Note that DEBUG=1 is absent (it is added by default by Xcode) - if defined, this brings in AssertProc. Define NDEBUG on release builds and omit the debug defines.
The Stg... functions are part of the MS implementation of Structured storage as you stated, but should not be referenced on a Mac, the Schemasoft implementation being used.
Okay I've been searching for hours to try and solve this but nothing has worked. This problem is very similar to other posts, but I none of their solutions work.
So I am writing an OpenGL program using glew and glfw and for some reason I am unable to get the program to compile. The error is on the include statement:
#include <GL/glfw.h>
and the error says 'GL.glfw.h' file not found.
I have followed all the instructions on the
GLFW-2.7.8 Release Notes
web page, which includes making glfw, and then importing the static library libglfw.a into Xcode. The library does show up under Build Phases -> Link Binary with Libraries, but apart from that Xcode doesn't seem to recognize it. For example, under the File Inspector it detects the file type as "Default - data".
The static library is configured for 64-bit architecture, which I am running.
I have tried changing the search paths under Build Settings.
I have the following frameworks included: Cocoa, OpenGL, and IOKit.
Please let me know if there is any more information you need to help me solve this problem and thank you for reading.
It turns out my glew was not importing correctly and so glfw did not work either.
These are the steps I took:
Changed the Base SDK from Latest OSX (10.8) to Current OSX.
After doing this, I "reduced" the error to an Apple Mach-O Linker (Id) error. Next:
Added -lGLEW to Other Linker Flags.
Added /opt/local/include/ to the header search paths
Added /opt/local/lib/ to the library search paths
Here is where I found my answer.
I'm very new to OMNeT++ and I'd like to use the serialization-library contained in the boost framework. However, when trying to use it, I get quite many errors such as:
Description Resource Path Location Type
undefined reference to `boost::archive::archive_exception::~archive_exception()'
OmCCN line 36, external location: /home/alexander/UniBE/BT/simulator/boost-compiledLibs
/include/boost/serialization/throw_exception.hpp C/C++ Problem
. I guess the problem is that I didn't yet link the compiled library in OMNeT. I've had a look at the makefile but any changes there are worthless since it is generated automatically by makemake. Furthermore, trying to access the menu item 'makemake' in project > properties > OMNeT++ IDE throws an error (The currently displayed page contains invalid values).
Can anyone give me a hint concerning what the error could cause or how to link the compiled library correctly?
Any hints are very appreciated!
cheers
alex
First you should get the library files.
For example in Ubuntu you should install these two packages: libboost1.46-dev, and libboost-serialization1.46-dev. Header files will be installed in usr/include/boost and library files will be installed in usr/lib.
To link the serialization library to your program:
Right click on your project and click properties. Then go to OMNET++ > Makemake.
find the Link tab, and in the "Additional objects to link with: (wildcards, ..." section, specify the path to your serialization library (say /usr/lib/libboost_serialization-mt.a).
I'm using the Boost Windows installer provided by boostpro.com and already have all the compiled binaries present in my boost_1.44/lib folder. However, when I'm trying to use the boost filesystem library, I'm getting a build error saying that
LINK : fatal error LNK1104: cannot open file 'libboost_system-vc90-mt-gd-1_44.lib'
I'm using Visual Studio 9, and I don't have a file called 'libboost_system-vc90-mt-gd-1_44.lib'. Any ideas on what I should do next?
You either need to compile the variant of Boost with "threading=multi runtime-debugging=on variant=debug" as that's not a variant that normally comes with the BoostPro installer (AFAIK); or switch your project to use a different variant. Most likely you need to turn off the "runtime-debugging=on" in VC, which translates to turning off the debug STD. See the Getting Started for what the name of the library it's asking for means.