-
Notifications
You must be signed in to change notification settings - Fork 33
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
cmake error #5
Comments
Run I STRONGLY recommend using the cmake GUI to configure the project, because it has a built-in file browser where you can choose locations. |
Using Andy's latest lib, we can successfully compile/link/run on OSX (10.12.6), so long as we set the path to the lib in DYLD_LIBRARY_PATH: ...SBMLsolver/binaries/alpha_0.0002/lib$ otool -L libsbmlsolver.dylib $ export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:SBMLsolver/binaries/alpha_0.0002/lib |
Cool!
Tested on win/mingw, and osx/gcc and linux/gcc?
…On Thu, Oct 11, 2018, 4:08 PM Randy Heiland ***@***.***> wrote:
Using Andy's latest lib, we can successfully compile/link/run on OSX, so
long as we set the path to the lib in DYLD_LIBRARY_PATH:
...SBMLsolver/binaries/alpha_0.0002/lib$ g++-8 test_mx.cpp -I../include
-L. -lsbmlsolver
...SBMLsolver/binaries/alpha_0.0002/lib$ a.out
dyld: Library not loaded:
/Users/andy/src/sbmlsolver_build/lib/libsbmlsolver.dylib
...SBMLsolver/binaries/alpha_0.0002/lib$ otool -L libsbmlsolver.dylib
libsbmlsolver.dylib:
/Users/andy/src/sbmlsolver_build/lib/libsbmlsolver.dylib (compatibility
version 0.0.0, current version 0.0.0)
/usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version
10.9.0)
/usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current
version 5.4.0)
/usr/lib/libform.5.4.dylib (compatibility version 5.4.0, current version
5.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version
400.9.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
1252.50.4)
$ export
DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:SBMLsolver/binaries/alpha_0.0002/lib
...SBMLsolver/binaries/alpha_0.0002/lib$ a.out
we’re good, made a solver, ready to use itready to use the scalar system,
connect it to our compartment
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKubcG0M6us2_kNrMrTywdloy0XmtZYDks5uj6VZgaJpZM4XVQZQ>
.
|
Only the best of those 3 so far 😉
The other 2 next.
On Thu, Oct 11, 2018 at 4:48 PM Paul Macklin <[email protected]>
wrote:
… Cool!
Tested on win/mingw, and osx/gcc and linux/gcc?
On Thu, Oct 11, 2018, 4:08 PM Randy Heiland ***@***.***>
wrote:
> Using Andy's latest lib, we can successfully compile/link/run on OSX, so
> long as we set the path to the lib in DYLD_LIBRARY_PATH:
> ...SBMLsolver/binaries/alpha_0.0002/lib$ g++-8 test_mx.cpp -I../include
> -L. -lsbmlsolver
> ...SBMLsolver/binaries/alpha_0.0002/lib$ a.out
> dyld: Library not loaded:
> /Users/andy/src/sbmlsolver_build/lib/libsbmlsolver.dylib
>
> ...SBMLsolver/binaries/alpha_0.0002/lib$ otool -L libsbmlsolver.dylib
> libsbmlsolver.dylib:
> /Users/andy/src/sbmlsolver_build/lib/libsbmlsolver.dylib (compatibility
> version 0.0.0, current version 0.0.0)
> /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version
> 10.9.0)
> /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current
> version 5.4.0)
> /usr/lib/libform.5.4.dylib (compatibility version 5.4.0, current version
> 5.4.0)
> /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version
1.2.11)
> /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version
> 400.9.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
> 1252.50.4)
>
> $ export
> DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:SBMLsolver/binaries/alpha_0.0002/lib
> ...SBMLsolver/binaries/alpha_0.0002/lib$ a.out
> we’re good, made a solver, ready to use itready to use the scalar system,
> connect it to our compartment
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#5 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AKubcG0M6us2_kNrMrTywdloy0XmtZYDks5uj6VZgaJpZM4XVQZQ
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABsVRap_2PHFUBoRhVc8ysQ3ZWUcgSylks5uj66xgaJpZM4XVQZQ>
.
|
Glad to hear it works in mingw. Good luck in OSX! :-)
On Thu, Oct 11, 2018, 4:57 PM Randy Heiland <[email protected]>
wrote:
… Only the best of those 3 so far 😉
The other 2 next.
On Thu, Oct 11, 2018 at 4:48 PM Paul Macklin ***@***.***>
wrote:
> Cool!
>
> Tested on win/mingw, and osx/gcc and linux/gcc?
>
> On Thu, Oct 11, 2018, 4:08 PM Randy Heiland ***@***.***>
> wrote:
>
> > Using Andy's latest lib, we can successfully compile/link/run on OSX,
so
> > long as we set the path to the lib in DYLD_LIBRARY_PATH:
> > ...SBMLsolver/binaries/alpha_0.0002/lib$ g++-8 test_mx.cpp -I../include
> > -L. -lsbmlsolver
> > ...SBMLsolver/binaries/alpha_0.0002/lib$ a.out
> > dyld: Library not loaded:
> > /Users/andy/src/sbmlsolver_build/lib/libsbmlsolver.dylib
> >
> > ...SBMLsolver/binaries/alpha_0.0002/lib$ otool -L libsbmlsolver.dylib
> > libsbmlsolver.dylib:
> > /Users/andy/src/sbmlsolver_build/lib/libsbmlsolver.dylib (compatibility
> > version 0.0.0, current version 0.0.0)
> > /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version
> > 10.9.0)
> > /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current
> > version 5.4.0)
> > /usr/lib/libform.5.4.dylib (compatibility version 5.4.0, current
version
> > 5.4.0)
> > /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version
> 1.2.11)
> > /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version
> > 400.9.0)
> > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version
> > 1252.50.4)
> >
> > $ export
> >
DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:SBMLsolver/binaries/alpha_0.0002/lib
> > ...SBMLsolver/binaries/alpha_0.0002/lib$ a.out
> > we’re good, made a solver, ready to use itready to use the scalar
system,
> > connect it to our compartment
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <
>
#5 (comment)
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/AKubcG0M6us2_kNrMrTywdloy0XmtZYDks5uj6VZgaJpZM4XVQZQ
> >
> > .
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <
#5 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ABsVRap_2PHFUBoRhVc8ysQ3ZWUcgSylks5uj66xgaJpZM4XVQZQ
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKubcOymyy0Z7X0wrMw_FQVw306HSEQwks5uj7DAgaJpZM4XVQZQ>
.
|
There was a time when Mac OS used to be the best of three, but that time has come and gone. From a dev environment, there’s simply no question than MS Visual Studio is the best one ever written. From an operating system perspective (kernel design, consistency of API), Windows again wins. Quality of desktop apps, well, they’re all going downhill (though with Linux, it started at rock bottom, and never left, so I guess it can’t go downhill anymore) Windows has made great strides in usability, and macOS has continued to go downhill since Steve Jobs death. |
After building the llvm and sbmlsolver_dep stuff, I try to build sbmlsolver: heiland@ubu18:~/git/sbmlsolver/build$ cmake -DSBMLSOLVER_DEP_DIR=/home/heiland/local .. -- Configuring incomplete, errors occurred! |
Please see previous comments. The Here, you can also choose what project file to generate for your IDE of choice, be it Visual Studio on Windows, Eclipse, or Xcode, or even KDevelop. It should look like this when you configure it: |
I know it's not an env var. Using "-D" is how you set cmake vars. I spent a few years using cmake regularly. I never liked nor used the gui version, nor should it be necessary. Everything's doable from the CLI. Nor do I plan to use any framework for cmake. Sorry. Do you know why, exactly, it reports "no LLVM installation was found" ? |
Providing the llvm-config gets me farther, but still errors (next). Perhaps if you post your entire CMakeCache.txt, it may shed some light? heiland@ubu18:~/git/sbmlsolver/build$ cmake -DSBMLSOLVER_DEP_DIR=/home/heiland/local -DLLVM_CONFIG_EXECUTABLE=/home/heiland/local/llvm-config .. -- The C compiler identification is GNU 7.3.0 CMake Error at cmake/FindLLVM.cmake:114 (STRING): CMake Error at cmake/FindLLVM.cmake:116 (STRING): CMake Error at cmake/FindLLVM.cmake:117 (STRING): CMake Error at cmake/FindLLVM.cmake:118 (STRING): CMake Error at cmake/FindLLVM.cmake:121 (string): CMake Error at cmake/FindLLVM.cmake:124 (STRING): CMake Error at cmake/FindLLVM.cmake:125 (STRING): CMake Error at cmake/FindLLVM.cmake:132 (STRING): CMake Error at cmake/FindLLVM.cmake:133 (STRING): CMake Error at cmake/FindLLVM.cmake:134 (STRING): CMake Error at cmake/FindLLVM.cmake:135 (STRING): CMake Error at cmake/FindLLVM.cmake:136 (STRING): CMake Error at cmake/FindLLVM.cmake:137 (STRING): CMake Error at cmake/FindLLVM.cmake:138 (STRING): CMake Error at cmake/FindLLVM.cmake:139 (STRING): CMake Error at cmake/FindLLVM.cmake:140 (STRING): -- LLVM_DEFINITIONS: -- LLVM_LIBRARIES: -- Configuring incomplete, errors occurred! |
You need to run Your dep install path bin, i.e. |
Also, when you ran the sbmlsolver dep build, did you run the make install also? It's strange that your sbmlsolver_dep install dir does not have a bin subdir. |
Also, you should be able to execute the
|
I switched back to OSX (from Ubuntu) to try to build from source. My previous success building a simple test was on OSX, but used your libs/headers. I was using cmake 3.11.2 and kept getting this error: It took me awhile to realize it was not coming from the CMakeLists.txt in your sbmlsolver root dir, but the one in the /src dir. Duh. The error was due to this section: Oh, and no, I'm still not using ccmake (the GUI). I did attempt it at one point in this slog, but, as expected, it automatically picks up my Xcode stack and I want to use our/PhysiCell g++ w/ OpenMP stack. Oh, and I don't want to have to reset all the entries that need to be reset every time I open the GUI (which will be many times). That's the beauty of specifying CMake vars from the shell. As I mentioned, I used CMake for a few years. I've been through this world. This is the workflow that I use and, IMO, is the easiest for new users. Copy/paste. So, this is what I do/now have (and this is without appending my PATH to use the ~/local/bin/llvm* commands, including llvm-config, built previously): ~/dev/sbmlsolver_build$ cmake -DCMAKE_C_COMPILER=/usr/local/bin/gcc-8 -DCMAKE_CXX_COMPILER:FILEPATH=/usr/local/bin/g++-8 -DSBMLSOLVER_DEP_DIR=$HOME/local -DCMAKE_INSTALL_PREFIX=$HOME/local ~/git/sbmlsolver ~/dev/sbmlsolver_build$ ll lib/ Next steps:
|
My own build working on OSX:
but need to append to DYLD_LIBRARY_PATH:
|
On Ubuntu 18.04, I upgraded my cmake to:
installed curses (otherwise had an error when running cmake to configure sbmlsolver):
appended the path to the new shared libs and made llvm-config available in my PATH
Ran cmake:
Get an error when compiling:
There seems to be lots of online discussion of such errors, e.g. link Oddly, in spite of the linking errors above, it does create a lib:
but a blind attempt to use it in our test pgm fails, not surprisingly:
|
I haven't tested the new build on Linux yet, but this is a trivial fix. I removed a line of the unix build. I know this exact error, and what line to charge to fix it. Just let me get a Linux installed, and I'll get you binaries, and I'll even get you a We need to start talking about the API and then I'll provide binaries for all three packages on a daily basis. I'll look into how GitHub continuous integration with Travis works, so that'll automatically compile and build on each checking. |
Are you saying you made the fix and committed it? I can't see an update,
but would like to test when it's done.
…On Sat, Oct 13, 2018 at 8:42 PM Andy Somogyi ***@***.***> wrote:
I haven't tested the new build on Linux yet, but this is a trivial fix. I
removed a line of the unix build.
Just let me get a Linux installed, and I'll get you binaries, and I'll
even get you a .deb.
We need to start talking about the API and then I'll provide binaries for
all three packages on a daily basis.
I'll look into how GitHub continuous integration with Travis works, so
that'll automatically compile and build on each checking.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABsVRXrArT228Dn5WaebEvXY0Z57OxmKks5ukohhgaJpZM4XVQZQ>
.
|
I haven't made the fix, but I know what the fix is. I'll try to test it on Linux maybe tomorrow, then get binaries out for Linux. I make binaries that are Linux distro independent. |
Hopefully what I shared about running cmake from the shell (rather than the
GUI) will be useful if/when you use CI, e.g., Travis.
…On Sat, Oct 13, 2018 at 9:17 PM Andy Somogyi ***@***.***> wrote:
I haven't made the fix, but I know what the fix is. I'll try to test it on
Linux maybe tomorrow, then get binaries out for Linux. I make binaries that
are Linux distro independent.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABsVRVF7-G5YDTDKXG8b3vkkGq9ornVrks5ukpC0gaJpZM4XVQZQ>
.
|
~/git/sbmlsolver$ export SBMLSOLVER_DEP_DIR=/Users/heiland/dev/sbmlsolver_install
~/git/sbmlsolver$ mkdir build
~/git/sbmlsolver$ cd build
~/git/sbmlsolver/build$ cmake ..
-- The C compiler identification is AppleClang 9.0.0.9000039
-- The CXX compiler identification is AppleClang 9.0.0.9000039
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:29 (if):
if given arguments:
Unknown arguments specified
The text was updated successfully, but these errors were encountered: