- #Cmake include directories visual studio how to#
- #Cmake include directories visual studio install#
- #Cmake include directories visual studio 64 Bit#
- #Cmake include directories visual studio license#
I would not recommend anything other than MKL on Windows however.See Installing and Using Packages Example: sqlite for a fully worked example using CMake.
#Cmake include directories visual studio how to#
Basically you need to figure out how to stick MKL into CMake, and then set the appropriate options in the nf.
#Cmake include directories visual studio license#
Now you can complicate this process further if you have a license of Intel's MKL library.
Get the VS2008 圆4 windows SDK ( ) and figure out how to use it (you probably just need to create that environment variable, but I'm not 100% on this) This is not guaranteed to be a perfect fix, but I have not noticed many issues with it.ģ.
If you don't have VS2008, you can create an environment variable "VS90COMNTOOLS", and give it exactly the same path that the pre-existant environment variable "VS100COMNTOOLS" has. If you have VS2008, use the VS2008 command prompt to build canteraĢ. This is because Python is built with VS2008, and by default it looks for VS2008's version of vcvarsall.bat.ġ. If you run into a problem building the python interface with an error something like "missing vcvarsall.bat" conf lives), now you should be able to call python scons (each one in series)ġ3. in the VS Command prompt, cd to the Cantera/src directory (where your. Sundials_libdir = 'C:\\Program Files\\Path\\To\\Sundials\\lib'Įnv_vars = 'all' #important, lets SCons get all your path variables etc.īuild_thread_safe = True #optional, but you have the boost libraries so why not!īoost_inc_dir = 'C:\\Program Files\\Path\\To\\Boost\\boost_1_55_0'īoost_lib_dir = 'C:\\Program Files\\Path\\To\\Boost\\boost_1_55_0\\lib64-msvc-10.0'ġ2. Sundials_include = 'C:\\Program Files\\Path\\To\\Sundials\\include' Prefix = 'C:\\Program Files\\Cantera' #or wherever You're almost there, now is mostly build settings in your nf file.
#Cmake include directories visual studio install#
python setup.py install (Make sure you added your Python install to your path, IIRC, Anaconda does this for you)ġ1. Open up the Visual Studio command line (it's nice and helpful, it sets all your paths etc for you)ĩ. You may or may not need to change the idasRoberts_FSA_dns settings to compile as C++ (I think it was resolved in 2.5.0)ĥ. You can generally substitute VS2010 for VS2008 in those instructions. This ( ) page is a bit old, but has very good instructions on how to do so. Use CMake to build Sundials using Visual Studio as your compiler.
#Cmake include directories visual studio 64 Bit#
You can also use the 64 bit install directly from, and use Christopher Gothke's page ( ) to get all your libraries (i.e. Install python directly (not under cygwin) - I use Anaconda ( ) as it comes packaged with matplotlib/numpy. It can be done, but generally it's not recommended.ġ. So basically mixing compilers is bad idea. My question here is: Does building sundials with -enable-shared flag circumvent this compiler issue? I proceed nevertheless (with g++ as the compiler on Cygwin) and succeed in building sundials. Setting environment variables directly by running the MSVC command prompt also fails. bat files must be discarded since their execution requires elevation. This thread talks about the workaround, but all of the alternatives mentioned with editing the. I would have liked to have built Sundials with the 64-bit MSVC compiler but couldn't call it from Cygwin ( bash: cl not found). Now I'm not certain if I can use libraries/includes built for sundials using g++ later in MSVC. This builds sundials (2.5.0) using g++ taken from Cygwin. Download the sundials source ( ) and build from Cygwin (./configure & make & make install).
0 kommentar(er)
