Page 1 of 3

Compiling Pioneer

Posted: Sun Jan 04, 2015 8:20 pm
by nick
Happy New Year!

Compiling Pioneer using MSVC.

I've followed the instructions https://github.com/pioneerspacesim/pion ... PILING.txt but get "no such file or directory" errors.
E.g. Cannot open include file: 'sigc++/sigc++.h': No such file or directory (this file is in the third party source.)

Before I start adding include/source folders to the solution to get it to compile, I thought I'd check whether there's something I've missed.

Side by side in a single folder I have

pioneer-master\
pioneer-thirdparty-master\

which were downloaded as zip and extracted (I'm not familiar with GitHub).
The solution file is pioneer-master\win32\vc2013Express\pioneer.sln
and the third party folder contains two folders "source" and "win32" (and other files).

I guess I have to set up include/source folders in the solution, but just checking here incase I've done something wrong!

I've just spotted that the thirdparty folder stucture contains a lot of solution files - do I have to build these first?

Thanks

Re: Compiling Pioneer

Posted: Sun Jan 04, 2015 10:09 pm
by FluffyFreak
No, just rename the folder "pioneer-thirdparty-master" to "pioneer-thirdparty" and it should work.

Re: Compiling Pioneer

Posted: Sun Jan 04, 2015 10:30 pm
by FluffyFreak
The reason for this is that the paths are relative and look for a path called "../pioneer-thirdparty", but your folder has a different name.

You don't need to build any of the sln files within pioneer-thirdparty itself, it's all ready to go.

Re: Compiling Pioneer

Posted: Mon Jan 05, 2015 6:18 am
by impaktor
OK, this is the second post on this issue. I'd like to understand who/why something slaps on the branch name on the folder?

@Fluffyfreak: is this something MSVC does? Or is it when you download the source as a tarball from github that it happens?

It might be worth adding a caveat to the COMPILE.txt file warning about this. But I'd like to understand it first.

Re: Compiling Pioneer

Posted: Mon Jan 05, 2015 8:46 am
by FluffyFreak
I think it's when you grab it as a tarball, you get the filename something like "repository-branch" so if you grab pioneer-thirdparty's master branch you get a zip file called "pioneer-thirdparty-master".

If you do a checkout from Git you can force it call the folder whatever you want but mostly it will just be the repository name.

MSVC doesn't do anything with source control automatically, though it does now have some features that would let it interact with it.

Re: Compiling Pioneer

Posted: Mon Jan 05, 2015 8:45 pm
by DraQ
Would it be possible to get up-to-date project file/build instructions for non-MSVC compiler and IDE under windows (for example C::B + MINGW)?

Re: Compiling Pioneer

Posted: Mon Jan 05, 2015 9:25 pm
by FluffyFreak
There aren't any instructions for Windows builds that don't use Visual Studio.

Luomu made some files to create C::B / MinGW but he's not involved in the project anymore and no-one has maintained those files so even if they generate valid projects etc I don't think they will build the project anymore.

Could be a good project to update and get working again.

Re: Compiling Pioneer

Posted: Mon Jan 05, 2015 10:40 pm
by nick
Thank you! Successful debug build :)

I changed thirdparty folder name from "pioneer-thirdparty-master" to "pioneer-thirdparty".
The incorrect name of the thirdparty folder came from GitHub (download as zip).

Re: Compiling Pioneer

Posted: Tue Jan 06, 2015 7:57 am
by impaktor
@nick good to hear!

If anyone else wan't to supply compilation instructions for any other system missing, such as C::B + MINGW, then please feel free, and we'll update the docs.

Re: Compiling Pioneer

Posted: Tue Jan 06, 2015 8:47 am
by FluffyFreak
Glad to hear you got it working nick.

You got any plans or just curious at this point?