conan-io / conan-io/docs

[question] Integrate conan into development tool chain, e.g. standard make files and IDEs

Open
#587 9 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
125
Forks
382
Avg merge
22h 39m
Merged PRs (30d)
21

Description

Dear conan-developers,

I'm currently using conan 1.1.1. with RHEL and try to evaluate how to integrate conan in our tool chain. Thus, I want to create packages, use packages, CI them, and adapt my tools to work with conan.
The documentation is really good, but I'm missing a whole picture/tutorial how to integrate conan, see also:
https://github.com/conan-io/docs/issues/32
To be more specific: I'm using Netbeans IDE which generates makefiles for my c/c++ projects.
What is the suggested way to integrate conan into the following example:
MPI-Helloworld:
I've successfully created a conan package for openmpi and a new C-Application project, which basically uses MPI to say helloworld from multiple processes. Netbeans generates the makefiles for the building process (as well as tests, which I'll ignore here).
Now, I want to use the conan-openmpi package I've build. The examples mostly shows how to integrate it into cmake, only mentioning, that make is also supported. What's the recommended way to use the include-/libdirs in my standard makefile? Shall I use the conan txt-generator and put the paths into my makefile? If so: a manual process would not be feasible for more complex projects. Thus, should I script this process or is it better to use conan to build my mpi-helloworld?
The next step is to create also a package for my mpi-helloworld. Then I'll have to adapt my IDE, i.e. adding the includes and libs into my IDE-properties (for sake of tracing code and navigate also into my openmpi library). At this point, I could of course work with symlinks or is there better way, like replacing the make command with a conan create and using the Autotools with conan to resolve my include/lib-path?
Finally, after the local integration, I want upload the code to a remote git-repo which triggers Jenkins and publish the artefact into artifactory (e.g. Jenkinsfile).
A lot of the pieces are described in the docs, but it is - at least for me - hard to get a full picture. A How-To article would be great!
I understand, that you can't cover all the topics, like specific IDEs, but maybe you can give an idea how conan would be used in such a environment?
Thank you & kind regards!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.