Issues with Compiling OpenVSP 3.31

[Jon Watts]

Hello all,

I know this has been a discussed issue in the past for previous versions of OpenVSP, and I did manage to successfully compile 3.26 last year. However for some reason, for the life of me I cannot figure out why I cannot complete the process for 3.31.

I am using Python 3.9.15 (as that was the default that came with the latest distribution of Anaconda), I have reinstalled CMake, Doxygen, SWIG and Visual Studio and tried running through the process a few times and cannot get passed the initial library build process. I get approximately 2500 warnings in Visual Studio each time it tries to build them.

I recognise that for the developers this is probably the millionth time where someone has asked for assistance on this, my apologies for adding to the list, but I wasn't sure if anyone else had experienced anything similar when attempting to compile 3.31.

Any help would be very much appreciated and I will happily answer any questions or provide more information if you need it!

Kind regards,

Jon

[Rob McDonald]

Warnings are generally harmless -- but annoying.  A new version of Visual Studio might be sensitive to something that past versions were OK with this.  Such is the constant evolution of compilers.

Are there any error messages buried in that mess?  After the Library build fails, you can try starting it again.  It should skip any files that are already compiled and it will re-try to compile anything that failed.  This can be a good way to narrow the flood of messages down to the errors (not the warnings).

Rob

--
You received this message because you are subscribed to the Google Groups "OpenVSP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/d1c5b7af-4872-4499-8f0d-243fdbefa990n%40googlegroups.com.

[Jon Watts]

Hi Rob,

Thank you for your quick response - I have been juggling trying to sort this with some other work and have been battling away with it to try to figure out what is going on. There does seem to be a significant difference in the response during the compiling process when using Visual Studio 2017 vs. 2022. It took me a long time to track down a way of installing the older version, but it still gave me 18 errors and 3 warnings. The build output was also "14 succeeded, 1 failed" if that helps at all. I have copied an image of the full error and warning list that Visual Studio outputs when first attempting to build the libraries.

Any more feedback or suggestions would be greatly appreciated and apologies in advance if I am being a moron, but for the life of me I cannot work out what is wrong.

Kind regards,

Jon

[Jon Watts]

I have just found the associated error notes with what seems to be causing the vast majority of the issues, I have pasted that below.

I'm not sure if this helps at all, but I thought it might!

Kind regards,

Jon

[Jon Watts]

And in case it is of benefit, attached here is also the output text from the window in CMake when configuring and generating the library files.

Kind regards,

Jon

[Rob McDonald]

I generally strive to compile FLTK with libpng support turned off.  OpenVSP does not use FLTK's libpng -- if you can turn it off, then perhaps you don't need to worry about this.

When visual studio stops after a bunch of errors and/or warnings, it is often useful to re-build immediately.  When you do this, it will re-try everything that failed (error) or that did not finish, but it will ignore everything that finished with success (including warnings).  By re-running a few times, you can get down to just the files that are failing -- which can sometimes help find the problem.

Rob

[Jon Watts]

Hi Rob, thank you for the recommendation regarding FLTK - I am not very savvy when it comes to compiling and I haven't been able to track down how to disable libpng support. If you could give me a heads-up on how to do that, that would be very much appreciated!

Kind regards,

Jon