conda-build maintainer here. I agree that having conda/conda-build as a
provisioner for general-purpose build environments would be helpful. I'm
afraid I don't understand what's missing or otherwise needs to change here,
though. If you have concrete suggestions (and better, PRs) for how to make
I cannot use conda-build if I am developing. Consider that I will be
editing the sources, compiling and running tests constantly. Going through
the conda-build process every time I need to check some changes would be
too much overhead. conda-build does a lot of things, it creates multiple
new
On Wed, Aug 15, 2018, 3:05 PM Sebastián Mancilla wrote:
> My 5c: Docker is just too annoying to work with if you are targeting users
> to run your packages.
>
> From the point of view of the final user of your "binary distribution"
> (some Docker image):
>
> - You have to figure out / copy paste
My 5c: Docker is just too annoying to work with if you are targeting users
to run your packages.
>From the point of view of the final user of your "binary distribution"
(some Docker image):
- You have to figure out / copy paste the proper docker command line to run
the container (mount volumes,
Our compiler activation scripts (highlighting the bit of most interest
to you I hope) are here:
https://github.com/AnacondaRecipes/aggregate/blob/master/ctng-compilers-activation-feedstock/recipe/activate-gcc.sh#L84-L101
On Wed, Aug 15, 2018 at 11:44 AM, Ray Donnelly wrote:
> Hi Sebastián,
>
>
Hi Sebastián,
Without having time to properly go through this, I feel I should
correct some technical inaccuracies, but *all* of your issues can be
sidestepped by using conda-build. Installation and RPATHs are always
very tricky for projects to get right so we side step any issues here
by running
Le mer. 15 août 2018 à 10:57, Ray Donnelly a
écrit :
> Docker is unnecessary overhead here and irrelevant to the question of
> which compilers to use when building conda packages (use ours or risk
> binary incompatibility with the rest of the ecosystems, please do not
> attempt to use e.g.
Docker is unnecessary overhead here and irrelevant to the question of which
compilers to use when building conda packages (use ours or risk binary
incompatibility with the rest of the ecosystems, please do not attempt to
use e.g. CentOS6 system compilers to compile modern software either!). Docker
Le mar. 14 août 2018 à 20:38, Sebastián Mancilla a
écrit :
> I wanted to try Conda for normal day-to-day C++ development, while having
> all the dependencies isolated from other projects and the base system.
>
> - Change the sources
> - Build
> - Run the tests
> - Repeat
>
Hi Sebastian,
Just
I wanted to try Conda for normal day-to-day C++ development, while having
all the dependencies isolated from other projects and the base system.
- Change the sources
- Build
- Run the tests
- Repeat
The most common workflow possible. I shouldn't go through conda-build for
that. There is nothing
Why are you not using conda-build here? Anaconda Distro and
conda-forge build countless CMake projects. It handles so much extra
stuff on top of building (DSO verification, rpath rewriting, more). If
your end goal is not conda packages then you can untar most sets of
conda-packages to make working
Thanks for the links.
The problem of setting CMAKE_BUILD_RPATH to $CONDA_PREFIX/lib is that
for binaries and libraries in the build tree, the list of RPATH
locations will be in the wrong order: the dependencies library path
will be first, and then the build tree. This will break the unit tests
if
See also:
https://gitlab.kitware.com/cmake/cmake/merge_requests/207
https://gitlab.kitware.com/cmake/cmake/issues/17483 (looks semi-related)
Ray Donnelly, who filed those issues, maintains the Anaconda compiler
toolchain -- so you are in good company hitting this issue. It looks like
some
The RPATH is not included when using Anaconda because CMake considers the
Anaconda lib path to be an implicit link directory (as reported by the
compiler). Look at `$build_dir/CMakeFiles/CMakeOutput.log` in the section
about "implicit link info".
The simplest work-around is to set BUILD_RPATH
I am trying to use Conda as a package manager for isolated C++ development
environments. But unfortunately, when using CMake with the Anaconda-provided
compilers [1] (which are used to compile the binary packages in the Anaconda
repositories), things do not work as expected.
I have a small test
15 matches
Mail list logo
