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

LibPack 3.0.0 does not support building in DEBUG mode #22

Open
chennes opened this issue Sep 4, 2024 · 4 comments
Open

LibPack 3.0.0 does not support building in DEBUG mode #22

chennes opened this issue Sep 4, 2024 · 4 comments
Assignees

Comments

@chennes
Copy link
Member

chennes commented Sep 4, 2024

Right now building the LibPack with the --mode=debug fails due to a set of issues. First and foremost, the pip install command needs to be modified to pull or compile debug versions of those packages. This is problematic for numpy, which requires a Fortran compiler. This Issue is intended as a catch-all to collect problems related to getting the debug-mode LibPack working.

@chennes chennes self-assigned this Sep 4, 2024
@oursland
Copy link

oursland commented Sep 4, 2024

We recently made a change to the Conda Windows Debug builds to use the RelWithDebInfo configuration. Would it be preferred to make a similar change to the Debug configuration when building on Windows?

@chennes
Copy link
Member Author

chennes commented Sep 4, 2024

Would it be preferred to make a similar change to the Debug configuration when building on Windows?

To which build? Of FreeCAD?

@oursland
Copy link

oursland commented Sep 4, 2024

Yes, FreeCAD. I see now that this issue is specific to LibPack.

@chennes
Copy link
Member Author

chennes commented Sep 4, 2024

Right -- for 95% of debugging, RelWithDebInfo is really what you want to be using on Windows, but for that last 5%, it would be nice to have a full debugging build of the whole stack so that FreeCAD can also be compiled with optimization off. I'd certainly welcome help getting the LibPack compiling in Debug, there are some "gotchas" in the process (like OCCT's insistence on making up its own naming convention...).

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

No branches or pull requests

2 participants