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

CMake: avoid confusion about two different fltk-config files in build tree #428

Open
Albrecht-S opened this issue Apr 11, 2022 · 1 comment
Assignees
Labels
CMake CMake bug or needs CMake support Prio 3 - Moderate e.g. unable to compile the software

Comments

@Albrecht-S
Copy link
Member

There has been confusion about two different fltk-config files being created in the CMake build tree. See this reply in an old thread in fltk.coredev ("Regression in CMake-based build"). Note that the mentioned regression has been fixed and has nothing to do with this issue here.

The reply mentions details which might be required for different build types, including multi-config builds like Xcode and Visual Studio.

This issue is a reminder to check this old thread and move the generated fltk-config files to appropriate places and/or generate the fltk-config file that is to be installed during the installation process if possible.

@Albrecht-S Albrecht-S self-assigned this Apr 11, 2022
@Albrecht-S Albrecht-S added CMake CMake bug or needs CMake support Prio 3 - Moderate e.g. unable to compile the software labels Apr 11, 2022
@Albrecht-S Albrecht-S added this to the Release FLTK 1.4.0 milestone Apr 11, 2022
@Albrecht-S
Copy link
Member Author

This issue will not be "fixed" in FLTK 1.4.x, I'll take care of this in 1.5.0 to avoid even more confusion for users already used to the way it is in 1.4.0 (Git branch master) as of today.

@Albrecht-S Albrecht-S removed this from the Release FLTK 1.4.0 milestone Apr 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMake CMake bug or needs CMake support Prio 3 - Moderate e.g. unable to compile the software
Projects
None yet
Development

No branches or pull requests

1 participant