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

Missing version on configure file path #58

Open
fbordignon opened this issue Mar 19, 2021 · 2 comments
Open

Missing version on configure file path #58

fbordignon opened this issue Mar 19, 2021 · 2 comments

Comments

@fbordignon
Copy link

Hi Guys, I've tried to figure this one out with no success.
I am building a custom app with SlicerCAT.
The path on lines 75 and similarly below are missing the last bit with the version, looks like ${Slicer_VERSION} is evaluating to an empty string.

@fbordignon
Copy link
Author

I've printed all cmake variables at install time and the ones with the slicer version on it are CMAKE_PROJECT_VERSION_MAJOR and CMAKE_PROJECT_VERSION_MINOR. If those are available on a common build (not inside a custom app) it may be better to use them. I can push a patch if it is the case.

Line 75 will be like this:

${CMAKE_BINARY_DIR}/${Slicer_QTLOADABLEMODULES_SHARE_DIR}/${MODULE_NAME}/${Slicer_MAIN_PROJECT_APPLICATION_NAME}-${CMAKE_PROJECT_VERSION_MAJOR}.${CMAKE_PROJECT_VERSION_MINOR}/kernel-template.json

@lassoan
Copy link
Contributor

lassoan commented Mar 22, 2021

Thanks for reporting this. We should use the custom application's main project name and version for kernel name and version.

So, if Slicer_MAIN_PROJECT_VERSION is non-empty then that should be used for version in CMake:

${CMAKE_BINARY_DIR}/${Slicer_QTLOADABLEMODULES_SHARE_DIR}/${MODULE_NAME}/${Slicer_MAIN_PROJECT_APPLICATION_NAME}-${Slicer_MAIN_PROJECT_VERSION}")

If Slicer_MAIN_PROJECT_VERSION is empty then ${Slicer_VERSION} should be used.

qSlicerJupyterKernelModule.cxx should be updated accordingly, too.

Please make the updates and check if it works both when the extension is built regularly and when it is built as part of a custom application.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants