Re: [sundials-users] Installation issue with SUNDIALS 3.1.1 on Windows

[Shah, V.]

Dear Andreas,=20

Thank you for sharing your approach on performing a clean installation of t=
he libraries.
Indeed, it helps a lot.

Kind regards,
Varun

-----Original Message-----
From: sundial...@llnl.gov [mailto:sundial...@llnl.gov] On Behalf Of=
Andreas Nicolai
Sent: Tuesday, 17 July 2018 22:14
To: SUNDIAL...@LISTSERV.LLNL.GOV
Subject: Re: [sundials-users] Installation issue with SUNDIALS 3.1.1 on Win=
dows

Dear Varun,

I use the following approach on Windows to get SUNDIALS working
alongside our solvers:

1. run cmake once to configure/generate the header file sundials_config.h
2. create a new VC project for a shared/static library (as you need it)
and set all build options such that they are compatible with your other
libs (make sure to add the includes to the various components)
3. add all the sources of the various modules in sundials you need

The advantage of this approach is that you get a clean library project
that you can manage just as your other projects and can integrate nicely
into your solution. Also, you will probably end up with a single library
for the entire sundials suite, make code management/dependency handling
easier (and easier to understand for your fellow coders).

-Andreas

Am 17.07.2018 um 13:51 schrieb Shah, V.:
> Dear All,
>=20
> =A0
>=20
> I am a new user of the SUNDIALS suite and will like to use CVODE for
> solving my system of stiff equations.
>=20
> =A0
>=20
> Currently, I am facing installation issues of the suite on Windows.
>=20
> =A0
>=20
> I followed the instructions in the USER_GUIDE and build the suite in
> buildir from the scrdir using the cmake gui. Further on Windows, the
> generator I used was Visual Studio 2017.=A0
>=20
> =A0
>=20
> Following the generation step, the execution of msbuild
> ALL_BUILD.vcxproj and msbuild INSTALL.vcxproj =A0commands did not produce
> the libraries and header files in the instdir, as it should have based
> on the USER_GUIDE.
>=20
> =A0
>=20
> Did anyone face similar issues with Visual studio 2017?
>=20
> =A0
>=20
> Please let me know, where am I going wrong or if there is a workaround.
>=20
> =A0
>=20
> Thanks in advance!
>=20
> =A0
>=20
> Best regards,
>=20
> Varun Shah
>=20
> =A0
>=20
> PS: On Linux based system, the installation of the suite went smoothly
> and I was able to run the built in examples.
>=20
> =A0
>=20
>=20
> ------------------------------------------------------------------------
>=20
> To unsubscribe from the SUNDIALS-USERS list: write to:
> mailto:SUNDIALS-USERS-...@LISTSERV.LLNL.GOV
>=20


--=20
Dr. Andreas Nicolai
Wiss. Mitarbeiter / Bereich: Modellierung und Simulation
Leiter Softwareentwicklung und -schulung

Technische Universit=E4t Dresden
Fakult=E4t Architektur
Institut f=FCr Bauklimatik
01062 Dresden

Telefon : +49 (351) 463-32298
E-Mail : andreas...@tu-dresden.de

Raum: BZW B 309, Zellescher Weg 17, 01069 Dresden

http://tu-dresden.de/bauklimatik


############################

To unsubscribe from the SUNDIALS-USERS list:
write to: mailto:SUNDIALS-USERS-...@LISTSERV.LLNL.GOV

############################

To unsubscribe from the SUNDIALS-USERS list:
write to: mailto:SUNDIALS-USERS-...@LISTSERV.LLNL.GOV

[Shah, V.]

Dear Cody Balos,

Thank you for the help.

I managed to install and run the example successfully on Windows 10 using Visual Studio 2017.

As pointed out by you, the issue was indeed with the selection of the shared and the static libraries configuring the project.

I tested both the options, i.e. building with either shared or static libraries and both work fine.

Thank you once again for your time!

Kind regards,
Varun Shah

From: sundial...@llnl.gov [mailto:sundial...@llnl.gov] On Behalf Of Balos, Cody Joe
Sent: Tuesday, 17 July 2018 18:01
To: SUNDIAL...@LISTSERV.LLNL.GOV

Subject: Re: [sundials-users] Installation issue with SUNDIALS 3.1.1 on Windows

Hello Varun,


I was able to replicate your issue. It seems that msbuild INSTALL.vcxproj fails if you configure the project to build both the static and shared libraries. I believe this is because on windows there is a .lib file for both shared and static libraries. Since the library is named the same the .lib is being overwritten and corrupted.

I am able to successfully build and install the libraries and header files on Windows 10 with Visual Studio 2017 if I configure the project to build exclusively static libraries or exclusively shared libraries. Here is how I setup the project directories:

C:\SUNDIALS
|---------- builddir
|---------- instdir
|---------- srcdir
|----------- config
|----------- doc
|----------- examples
|----------- include
|----------- src
|----------- test
|----------- CMakeLists.txt
|----------- INSTALL_GUIDE.pdf
|----------- LICENSE
|----------- README.md

I opened up Visual Studio 2017 as an administrator (since my instdir is in C:\SUNDIALS), then opened the visual studio command prompt. In the cmake-gui I chose the Visual Studio 15 2017 Win64 generator. I disabled one of BUILD_SHARED_LIBS and BUILD_STATIC_LIBS so that only shared or static libraries are built, and then proceeded with the INSTALL_GUIDE steps.


Regards,

Cody Balos
Software Developer @ LLNL


From: <sundial...@llnl.gov<mailto:sundial...@llnl.gov>> on behalf of "Shah, V." <V.S...@TUE.NL<mailto:V.S...@TUE.NL>>
Reply-To: sundials-users <sundial...@llnl.gov<mailto:sundial...@llnl.gov>>
Date: Tuesday, July 17, 2018 at 8:09 AM
To: "SUNDIAL...@LISTSERV.LLNL.GOV<mailto:SUNDIAL...@LISTSERV.LLNL.GOV>" <SUNDIAL...@LISTSERV.LLNL.GOV<mailto:SUNDIAL...@LISTSERV.LLNL.GOV>>
Subject: [sundials-users] Installation issue with SUNDIALS 3.1.1 on Windows

Dear All,

I am a new user of the SUNDIALS suite and will like to use CVODE for solving my system of stiff equations.

Currently, I am facing installation issues of the suite on Windows.

I followed the instructions in the USER_GUIDE and build the suite in buildir from the scrdir using the cmake gui. Further on Windows, the generator I used was Visual Studio 2017.

Following the generation step, the execution of msbuild ALL_BUILD.vcxproj and msbuild INSTALL.vcxproj commands did not produce the libraries and header files in the instdir, as it should have based on the USER_GUIDE.

Did anyone face similar issues with Visual studio 2017?

Please let me know, where am I going wrong or if there is a workaround.

Thanks in advance!

Best regards,
Varun Shah

PS: On Linux based system, the installation of the suite went smoothly and I was able to run the built in examples.

________________________________

To unsubscribe from the SUNDIALS-USERS list: write to: mailto:SUNDIALS-USERS-...@LISTSERV.LLNL.GOV

________________________________