-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix MODL_Coclustering double size in windows #97
Fix MODL_Coclustering double size in windows #97
Conversation
51f447c
to
05397ae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
J'ai vérifié sur ma branche: ça corrige bien le problème ;)
Question
- pourquoi continuer à se référer à MPI_SUFFIX si on ne compile pas cet exe avec MPI (cf. genum)?
Suggestion
- si tu change les commentaires, il faudrait homogénéiser avec ceux des autres CMakeLists.txt (en particulier celui de MODL)
Good question. This impacts the installation let's wait for @bruno-at-orange to weigh in.
Ok |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stop focusing on targets !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Je ne suis pas d'accord avec la modification des commentaires. Il faut que tu arretes de te focaliser sur les target. TOUT est target dans cmake. Par exemple pour, add_binary(TOTO) et add_executable(TITI) dans le commentaire, on ne va pas mettre qu'on ajoute la target TOTO et la target TOTI mais bien l'executable TOTO et la bibliothèque TITI car c'est ce qu'oin souhaite faire. Et que cmake passe par des targets, c'est secondaire et ça n'apporte absolument rien à la comprehension du fichier CMakeList qu'on est en train de commenter.
Ici en l'occurence on parle du binaire MODL_Coclustering ou du nom de ce binaire. D'ailleurs pour fedora on n'a pas du tout besoin de renommer la target mais bien le nom du binaire !!!
Mon commentaire n'était peut-être pas précis car je faisis un abus de le langage, en effet il ne faut pas renommer le binaire mais le nom du binaire, soit ! On aurait donc on fedora, binaries names built with mpi must be suffixed by _mpich
. Je pense qu'il est important de commencer le commentairte par on fedora
car ça ne concerne que fedora...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. I will be more precise for each target type (binary or library). I would keep separated the code for each of them to avoid bugs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was also a formatting error of cmake-format
I didn't mean to put On Fedora
after the title of the section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok si seulement correction du bug de l'issue
dd98f5e
to
d96ccb7
Compare
d96ccb7
to
10d575a
Compare
The MODL_Coclustering.exe executable in windows had doubled in size because the MSVC link option `/INCREMENTAL` was activated. This wasn't the case for the original build with VS projects.
10d575a
to
ac429b9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
"Dismissed" just to merge
The MODL_Coclustering.exe executable in windows had doubled in size because the MSVC link option
/INCREMENTAL
was activated.This wasn't the case for the original build with VS projects.