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

Fix MODL_Coclustering double size in windows #97

Merged

Conversation

folmos-at-orange
Copy link
Member

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.

@folmos-at-orange folmos-at-orange linked an issue Nov 2, 2023 that may be closed by this pull request
@folmos-at-orange folmos-at-orange force-pushed the 79-khiops-cc-size-is-twice-as-it-was-in-1011-in-windows branch from 51f447c to 05397ae Compare November 2, 2023 13:39
Copy link
Collaborator

@marcboulle marcboulle left a 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)

@folmos-at-orange
Copy link
Member Author

folmos-at-orange commented Nov 8, 2023

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)?

Good question. This impacts the installation let's wait for @bruno-at-orange to weigh in.

Suggestion

  • si tu change les commentaires, il faudrait homogénéiser avec ceux des autres CMakeLists.txt (en particulier celui de MODL)

Ok

Copy link
Contributor

@bruno-at-orange bruno-at-orange left a 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 !

Copy link
Contributor

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...

Copy link
Member Author

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.

Copy link
Member Author

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.

Copy link
Collaborator

@marcboulle marcboulle left a 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

@folmos-at-orange folmos-at-orange force-pushed the 79-khiops-cc-size-is-twice-as-it-was-in-1011-in-windows branch 3 times, most recently from dd98f5e to d96ccb7 Compare November 24, 2023 17:53
@folmos-at-orange folmos-at-orange force-pushed the 79-khiops-cc-size-is-twice-as-it-was-in-1011-in-windows branch from d96ccb7 to 10d575a Compare November 27, 2023 09:00
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.
@folmos-at-orange folmos-at-orange force-pushed the 79-khiops-cc-size-is-twice-as-it-was-in-1011-in-windows branch from 10d575a to ac429b9 Compare November 27, 2023 10:01
Copy link
Collaborator

@marcboulle marcboulle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@folmos-at-orange folmos-at-orange dismissed bruno-at-orange’s stale review November 27, 2023 12:42

"Dismissed" just to merge

@folmos-at-orange folmos-at-orange merged commit ad593d4 into dev Nov 27, 2023
40 checks passed
@folmos-at-orange folmos-at-orange deleted the 79-khiops-cc-size-is-twice-as-it-was-in-1011-in-windows branch November 27, 2023 12:43
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.

Khiops CC size is twice as it was in 10.1.1 in windows
3 participants