-
The generated `cget.cmake` file does include a `include_directories(SYSTEM ${CMAKE_PREFIX_PATH}/include)` statement.
However, it would be nice if it included a similar `link_directories(${CMAKE_PRE…
-
Hi,
I'm trying to create/install a package from a GitHub repo (that I do not own). The repo already uses CMake as its build system, so that's a positive start at least.
However, it seems the rep…
-
From @krlmlr:
> I'm getting bogus errors that seem to relate to the new registration code. I can't replicate them locally yet, but on Travis CI I'm getting test failures iff I use the all-new regis…
-
Hi,
Is there any advice/examples available of best practices for creating a cget recipe for a library that does not already use CMake?
Is there perhaps a way I can "inject" a custom CMakeLists.t…
-
I'm trying to figure out a sane way to allow sys admins to install just the library dependencies of an executable into the build tree, link to the libs statically and then install just the executable …
-
First, this project looks awesome.
I ran `cget install google/googletest`. Everything went fine.
But then I tried to start an empty folder and I wrote a `requirements.txt` containing only the li…
-
I am currently in the process of creating a re-usable controller for handling route actions. Unfortunately I am experience a strange issue with how `cgetAction` and `getAction` route names are being h…
-
I'm getting the following build errors on OS X when installing the XZ recipe. I'm able to build fine when running ./configure && make.
```
In file included from /Users/jonathonl/cget/cget/build/tmp…
-
Recipes installed in a requirements file are not immediately available. The following requirements file needs to be ran twice to work.
```
pfultz2/cget-recipes
xz
```
-