Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modern cmake (no include_directories) #665

Closed
wants to merge 3 commits into from

Conversation

nebatmusic
Copy link

STEPS TO MOVE TO MODERN CMAKE.

First rule : do not include_directories

@mathildemerle
Copy link

This seems to be an example of PR that needs to be done on medInria, as we said last meeting

@nebatmusic
Copy link
Author

nebatmusic commented Nov 12, 2020

This seems to be an example of PR that needs to be done on medInria, as we said last meeting

needs also to be done you mean.
Like #659.

@nebatmusic
Copy link
Author

Moder CMAKE. Think in term of modules. Keeps your flags to yourself
WIP illustation.
mediniria_module

@nebatmusic
Copy link
Author

This seems to be an example of PR that needs to be done on medInria, as we said last meeting

needs also to be done you mean.
Like #659.

This is an improvement of the PR done on medinria public medInria#610 . But in this PR they were some errors.
For example It did not follow the rule 2 : "never do a target_include_directories on a directory outside of your project"

@mathildemerle
Copy link

#659 is mandatory for MUSICardio, not medInria, this is a change in the minimal number of cmake. However, as far as i see, this PR should be done on medInria. You can talk about that to FlorentL

@nebatmusic
Copy link
Author

#659 is mandatory for MUSICardio, not medInria, this is a change in the minimal number of cmake. However, as far as i see, this PR should be done on medInria. You can talk about that to FlorentL

Ok. But it is in medInria3.2.x.

@Florent2305
Copy link
Collaborator

It's a Huge change for medInria3.2 but this PR contains some good changes.
Then maybe it's a good idea to propose this pr for medInria master (4.0)

@nebatmusic
Copy link
Author

It's a Huge change for medInria3.2 but this PR contains some good changes.
Then maybe it's a good idea to propose this pr for medInria master (4.0)

I do not agree. It is minor change in some package generation files for legacy code in order to follow modern cmake modern already available in medinria. It doesn't break any API. I think that changes that should be in 4 are those breaking some API (rule that I have heard a few days ago about LIB versioning).

@nebatmusic
Copy link
Author

What should be done in 4, is to tell HASTA LA VISTA to legacy code (I want to say update it of course).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants