https://github.com/stevetownsend/smartharvestse

AutoHarvest 2 Skyrim SE mod ported to CommonLibSSE
https://github.com/stevetownsend/smartharvestse

Last synced: about 1 month ago
JSON representation

AutoHarvest 2 Skyrim SE mod ported to CommonLibSSE

• Host: GitHub
• URL: https://github.com/stevetownsend/smartharvestse
• Owner: SteveTownsend
• License: gpl-3.0
• Created: 2020-03-26T19:24:34.000Z (almost 5 years ago)
• Default Branch: master
• Last Pushed: 2024-10-27T12:17:57.000Z (2 months ago)
• Last Synced: 2024-10-27T13:50:24.543Z (2 months ago)
• Language: C++
• Homepage:
• Size: 62.3 MB
• Stars: 18
• Watchers: 4
• Forks: 7
• Open Issues: 106
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Smart Harvest SE

https://www.nexusmods.com/skyrimspecialedition/mods/37091

## Building

The library builds using CMake. I don't use the Colorglass repository for CommonLibSSE-NG because I found it hard to work out what was going on. Instead, CMakeFiles.txt manually imports its dependencies using *FetchContent*.

Doing this brute force helped me understand CMake better, and makes it possible to experiment with other CommonLibSSE-NG variants. I don't plan to revert the build to use vcpkg.

CMake is confusing, no question. Things to know:

- it is a two-phase process: first *configure* to generate the build, then *build*

- once you have configured, you can only build that configuration until you change the configuration preset by removing the generated *CMakeFiles* and *CMakeCache.txt*, and re-running the configure step

- don't build in your source code directory, it clutters it up with cruft

- **multi-target generators** exist that allow build of different targets without reconfiguring, but that's just going to confuse me all over again.

1. Check out the code

2. Start a Visual Studio 20xx Powershell window to do the build

3. change directory to the SmartHarvestSE root directory you just checked out.

4. Configure using the appropriate preset *cmake -B ./build -S . --preset Logging-MSVC|Release-MSVC|Debug-MSVC*

5. Build using the matching **CMAKE_BUILD_TYPE**: *cmake --build ./build/ --config RelWithDebInfo|Release|Debug*

When you want to change the build you are working with, configure then build using the matching **CMAKE_BUILD_TYPE**.

Versioned build artifacts go into *./build/zip* in a subdirectory that matches the build config.

If you edit *CMakeFiles.txt* or other CMake files, manually delete *./build/CMakeCache.txt* and *./build/CMakefiles* to trigger full rebuild. This should not be necessary for vanila code edits.

## Dependencies

**CMake** minimum version per CMakeFiles.Txt

**Visual Studio 2022**, for its CMake Generator

**WinRAR** - rar.exe is used to compress the archive for release to Nexus. If you are just building locally, comment that part out at the end of *CmakeFiles.txt*

## Scripts

Scripts can be built using the Visual Studio Code Papyrus extension. There is a Papyrus project file **SkyrimSE.ppj** that should be edited according to your local setup.

Note: CMakeFiles is referring to all the generated CMakeFiles in your build directory... You are able to keep _deps_ around to save having to redownload the project dependencies