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

Make sure that debug dlls of OCC have different file names than from release build #5

Open
wwmayer opened this issue Aug 20, 2023 · 4 comments

Comments

@wwmayer
Copy link

wwmayer commented Aug 20, 2023

With the latest LibPacks the debug and release dlls of OCC have the same file names. This makes it very difficult to make a debug build of FreeCAD to use the debug build of OCC.

OCC's CMake build scripts used to have an option where for the debug build the suffix "d" was added to the dlls.

@chennes
Copy link
Member

chennes commented Aug 20, 2023

Thanks - is OCC the only library where we have to make this differentiation manually?

@wwmayer
Copy link
Author

wwmayer commented Aug 20, 2023

Yes, I think so.

@chennes
Copy link
Member

chennes commented Aug 21, 2023

OK - I'm working on a new LibPack that's got Qt6 and Python 3.11 in it, do you want me to also make a "backport" LibPack that updates the OCC but leaves everything else the same as the current LibPack?

@wwmayer
Copy link
Author

wwmayer commented Aug 21, 2023

do you want me to also make a "backport" LibPack that updates the OCC but leaves everything else the same as the current LibPack?

The problem has been reported in the forum where mixing OCC release dlls with a FreeCAD debug build can lead to a crash: https://forum.freecad.org/viewtopic.php?p=700327#p700327

I for myself don't need it because I still use my older LibPack that doesn't suffer from this issue. But if you are already working on a new LibPack with Qt6 it doesn't harm to prepare a backport LibPack. But don't forget to also provide a new debug version of netgen/nglib then.

Thanks!

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