Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

More install targets?

See original GitHub issue

Many projects have multiple requirements.txt to handle different needs in (take website for example) local dev, CI staging, production, etc. With Pipfile there are only default and dev.

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

kennethreitzcommented, Sep 21, 2017

0reactions

kennethreitzcommented, Sep 21, 2017

develop / production have been enough for the composer community, and i have faith that they are enough for us too.

Top Results From Across the Web

install — CMake 3.25.1 Documentation

The TARGETS form specifies rules for installing targets from a project. ... A target may be installed more than once to different locations....

Adding an install target in CMake - The Last Viking's Nest

Adding an install target in CMake ... CMake can do more than just build your software projects. It can also install them. CMake...

CMake install (TARGETS in subdirectories) - Stack Overflow

According to this bugreport, install(TARGETS) command flow accepts only targets created within the same directory.

eros/Tutorials/Install Targets

Description: This shows how to add install/uninstall targets to your package. This is most useful when building strictly c++ packages (no ros) within...

Feature Request: Allow install(TARGETS) to optionally also ...

The CMakeLists.txt in the install/ folder has the rules for installing the different targets. The way this installation works for us is that...