Engine
simple engine built on top of SFML (by TDSOJohn)
cmake-init-vcpkg-example
cmake-init generated executable project with vcpkg integration (by friendlyanon)
Engine | cmake-init-vcpkg-example | |
---|---|---|
1 | 19 | |
0 | 9 | |
- | - | |
0.8 | 5.6 | |
about 1 year ago | about 1 month ago | |
C++ | CMake | |
- | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Engine
Posts with mentions or reviews of Engine.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-12.
-
CMake/Make problem when compiling C++
I'm not 100% sure this is the correct place to post it because it might be a CMake/Make problem or a C++ one. So, I've just bought a M1 computer. First thing, I download homebrew and use it to install CMake and SFML. All works as expected, but then I clone and build my github repos. First one ( https://github.com/TDSOJohn/Engine ) works flawlessly, cmake generates the make file and CLang compiles everything. I also test the Engine by building the example I wrote, 0 problems, it links with SFML and everything runs smoothly.
cmake-init-vcpkg-example
Posts with mentions or reviews of cmake-init-vcpkg-example.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-18.
-
Clang-tidy ignore third party
If your dep is not on any of those, then you can write your own port with vcpkg very easily like this.
-
How would you create/maintain a new c++ project using modern tools/practices?
Are they only on git(hub)? You can write a vcpkg overlay port (example) or use FetchContent if the projects are FetchContent ready in a way that doesn't force FetchContent on people trying to build the project (example).
-
CMake/Make problem when compiling C++
Take a look at cmake-init, vcpkg and this example that shows how to pull dependencies from git(hub) using vcpkg's overlay ports.
-
How to download libraries with vcpkg?
cs50 doesn't appear to be present in the MS repo. No problem, you can write your own overlay port. You can find an example for that here: https://github.com/friendlyanon/cmake-init-vcpkg-example
-
Managing Newlib as a Project Dependency
You can take a look at vcpkg or Conan. Maybe vcpkg could be simpler here, because overlay ports are simpler to write than setting up Artifactory for Conan.
-
Best way to manage dependencies with c++?
Conan and vcpkg are the only options. I use them both, depends on what kinds of dependencies I want to pull. vcpkg is easier to setup custom one-off dependencies with using overlay ports, while Conan is faster at things if your profile fits one that has a pre-built binary in CCI. Both are trivial to integrate with a CMake project, see these examples for Conan and vcpkg.
-
Libraries
Here is an example that shows you how to write your own ports for libraries that don't have one provided by vcpkg. The alternative is doing it manually, but eh.
-
CMakePresets.json and vcpkg based GitHub Action workflows for C++
As part of the cmake-init examples I also have an example showing vcpkg integration with a CMake project with exact instructions on what that takes, which also involves CI.
-
Barbarian, an open and distributed Conan package index!
Overlay ports.
-
Problem with imported library
IMPORTED targets have directory scope, they aren't global like the other target types. Depending on what your project's type is and how it's used, the correct answer can vary from just requiring a path to be passed on the CLI to proper package management usage (e.g. vcpkg)
What are some alternatives?
When comparing Engine and cmake-init-vcpkg-example you can also consider the following projects:
cmake-init - The missing CMake project initializer
CPM.cmake - 📦 CMake's missing package manager. A small CMake script for setup-free, cross-platform, reproducible dependency management.
CAmusic - simple 1d cellular automata to MIDI program
steam-runtime - A runtime environment for Steam applications
conan-center-index - Recipes for the ConanCenter repository
Folly - An open-source C++ library developed and used at Facebook.
CMake - Mirror of CMake upstream repository
Jenkins - Jenkins automation server
gentoo - [MIRROR] Official Gentoo ebuild repository
cmake-init-fetchcontent - Example for optionally vendoring using FetchContent
icecream - Distributed compiler with a central scheduler to share build load
Engine vs cmake-init
cmake-init-vcpkg-example vs CPM.cmake
Engine vs CAmusic
cmake-init-vcpkg-example vs steam-runtime
cmake-init-vcpkg-example vs conan-center-index
cmake-init-vcpkg-example vs Folly
cmake-init-vcpkg-example vs CMake
cmake-init-vcpkg-example vs Jenkins
cmake-init-vcpkg-example vs gentoo
cmake-init-vcpkg-example vs cmake-init-fetchcontent
cmake-init-vcpkg-example vs cmake-init
cmake-init-vcpkg-example vs icecream