Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building/Compiling #14

Open
fireundubh opened this issue Oct 19, 2019 · 2 comments
Open

Building/Compiling #14

fireundubh opened this issue Oct 19, 2019 · 2 comments

Comments

@fireundubh
Copy link

Please note that this is developed against MSVC 2015, so other compilers may not work, and earlier versions of MSVC almost certainly won't due to C++11 support.

That's what the readme says, but Caprica.vcxproj is configured for ToolsVersion="15.0" and <PlatformToolset>v141</PlatformToolset>.

The project also contains paths for boost_1_58_0, but CMakeLists.txt is looking for:

find_package(Boost 1.52.0 COMPONENTS filesystem program_options REQUIRED)

Just trying to open the project in VS2015 was a pain, but opening the project in VS2017 was a breeze. That said, I can't get Caprica to compile due to a wide assortment of errors. I was wondering if you could fix this project up so that it can be compiled, as well as some build instructions.

@fireundubh
Copy link
Author

fireundubh commented Oct 19, 2019

Looks like a number of changes were made recently to support VS2017.

Code Change

Line 65 in main.cpp:

      if (filenameRef != "." && filenameRef != "..") {

Change to:

      if (filenameRef.compare(".") != 0 && filenameRef.compare("..") != 0) {

Project Changes

  • Add _HAS_AUTO_PTR_ETC; to preprocessor definitions. (Might need only the second one.)
  • Fix the include path to Boost.
  • Build Boost. (Steps below.)
  • Add D:/dev/boost_1_58_0/stage/lib; to the linker library directories.

Building and Configuring Boost

  1. Run VS2017 Developer Tools.
  2. Change the directory to where Boost was extracted (e.g., cd D:\dev\boost_1_58_0).
  3. Run bootstrap.
  4. Run b2 address-model=64.
  5. Run b2 build-type=complete.

@Orvid
Copy link
Owner

Orvid commented Oct 27, 2019

The code for Caprica hasn't been touched in > 2.5 years at this point, and I'd strongly recommend using the official Papyrus compiler included in the Creation Kit rather than Caprica. Caprica was only ever designed to be a workaround when the Creation Kit hadn't yet released.

I would accept PRs if you want to get it back up and running, but I have no plans to do so myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants