Compilation Errors

[ghost]

I am using Windows 10 and I have been following the instructions on http://fw4spl.readthedocs.io/en/dev/Installation/src/WindowsInstall.html. In the cmake-gui, I did not use the generator NMake Makefiles JOM but instead I used Visual Studio 15 2017 Win64. The generation was successful. Now I used Microsoft Visual Studio 2017 to compile the dependencies by using the BinPkgs solution file but I am getting these errors below.

I also have log files: logfiles.zip

By the way, I have read in https://github.com/fw4spl-org/fw4spl-deps/issues/9 that you mentioned that a precompiled binary will be released for Windows, are there any available?

[greenjava]

Hi,
Thank you for your interest with fw4spl and submitting your issue.
Visual Studio 2017 in not yet supported to build fw4spl and fw4spl-deps.

Currently only Visual 2015 (as mentioned in the doc) is officially supported.

Precompiled dependencies for Windows/Linux/macOS and Visual 2017 support is planned in the coming months.

Sorry for the inconvenience

[ghost]

Hi, this time I used the Visual Studio 14 2015 Win64 generator in the cmake-gui and the generation was successful. Now I used Microsoft Visual Studio 2015 to compile the dependencies by using the BinPkgs solution file and I am getting some errors. Can you help me out?

I also have log files: Logfiles.zip

If you do not have precompiled binaries for Visual 2017, do you have any for 2015?

[greenjava]

Hi,
OK, I recommend using the generator "NMake Makefiles JOM" to compile the dependencies (it's faster and it's the method we use here). I note the issue with this generator, thank you for your comment.
I'll try to upload MSVC2015 binaries today.

[ghost]

Hi, I did not use Jom since there were again errors occurring during the source code compilation which I could not solve. Jom also provides precompiled binaries but their link is broken (even the archives for the older versions). I had no choice but to use the Visual Studio generator.

Thanks, I appreciate your help and I'll be looking forward to the binaries.

[greenjava]

hum, strange, I have no problem to download jom (did you look here: https://wiki.qt.io/Jom ?)

The compilation with Visual Studio generator (compared to the Makefile generator) is different for some project, libarchive for example adds specific flags /weXXXX for debug build 😞. It requires to patch many lib.

I'll run the build to provide a clean precompiled version (we'll try to automate this for future versions 😉).

[ghost]

Yes, this is the page that is redirected when I try to download Jom. I also tried emailing the server administrator but didn't get any response from them. Could you possibly upload the file for me here? Maybe if I can install Jom, maybe creating the binary would be easier for you.

[greenjava]

Ok, the download mirror site proposed is down (jaist.ac.jp), embarrassing...
You can force the download on another mirror here:
Https://download.qt.io/official_releases/jom/jom_1_1_2.zip.mirrorlist
(http://master.qt.io/official_releases/jom/jom_1_1_2.zip seems ok)

[ghost]

Thanks I'll try it out. Please let me know when the binaries are ready!

[greenjava]

I've uploaded a debug and release version (tag 11.0.4) of the dependencies (built with Visual 2015 in x64):

• fw4spl-deps-debug-11.0.4_20170329_Win64_MSVC2015.zip
• fw4spl-deps-release-11.0.4_20170329_Win64_MSVC2015.zip

It's not yet "official" versions (kind of beta version), the process need to be automated in build farms.

[ghost]

Thanks for your help!

Sorry to bother you :( but I'm also having trouble building fw4spl in the cmake-gui with fw4spl-ar and fw4spl-ogre as the ADDITIONAL_PROJECTS. What could be the problem? Would it be too much to ask for a precompiled binary for fw4spl also? Thanks.

[greenjava]

Hi,
The problem here is in ADDITIONAL_PROJECTS value,
you must write CMake path in unix-style, with "/":
C:/FW4SPL/fw4spl/Dev/Src/fw4spl-ar;C:/FW4SPL/fw4spl/Dev/Src/fw4spl-ogre

Precompiled binary version for fw4spl is planned (it's the next cool feature), but this requires a lot of work for everything work properly (due to the particular 'bundle' architecture of fw4spl).