You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Why is the CMakeLists.txt unmaintained? Is it too difficult to structure the output files?
If so, I fixed the issue in my fork and I am open to share the idea with you
The reason will be displayed to describe this comment to others. Learn more.
Because next to now one used it. It was broken several times by not porting changes from the Makefile and each time it took month until someone noticed. I wanted to remove it completely, but it turned out that there're some usecases for it. So it was marked as unmaintained. It should work for "normal" builds, though.
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I agree that it is awkward to keep the two build systems...
CMakeLists.txt is necessary for Windows builds with MSVC compiler coz it can generate Visual Studio solutions. So I keep the CMakeLists.txt in my fork instead.
fb1a2b0
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.
Why is the CMakeLists.txt unmaintained? Is it too difficult to structure the output files?
If so, I fixed the issue in my fork and I am open to share the idea with you
fb1a2b0
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.
Because next to now one used it. It was broken several times by not porting changes from the Makefile and each time it took month until someone noticed. I wanted to remove it completely, but it turned out that there're some usecases for it. So it was marked as unmaintained. It should work for "normal" builds, though.
fb1a2b0
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.
Yeah, I agree that it is awkward to keep the two build systems...
CMakeLists.txt is necessary for Windows builds with MSVC compiler coz it can generate Visual Studio solutions. So I keep the CMakeLists.txt in my fork instead.