-
Notifications
You must be signed in to change notification settings - Fork 61
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
Can not build outside of a git repo #387
Comments
Interesting. Is this really critical? Can you just use the binaries for 1.2.1? Or check out that specific tag? Off the top of my head, I don't know if this is fixable or not, some of those dependencies carry over from Slicer SEM. If there is one person who knows the answer off the top of his head - it would be @jcfr! |
@fedorov, it's not absolutely critical for our projects, but anyone checking out your source code would not be able to build |
short answerTo be specific, out of source builds are supported. After checking out sources using git, it is possible to build the project in the directory of your choice. What is not supported is to build the project downloading the pre-generated source archives associated with Github Release. long answer
Checking out the source using git is expected to work, the following test confirms this:
In your Dockerfile, I suggest you use ninja (for automatic build parallelization) and do the following:
What does not work is building using the pre-generated source archive associated with GitHub release. proposed solutionUpdate
|
Thank you for chiming in @jcfr!
@blezek my point is that you can currently build from a github checkout, and you have binaries for all platforms. So far no one raised a concern about not being able to build from a source package. Is it really critical to be able to build from those source packages? |
Trying to build v 1.2.1 inside Docker, but gailed in super build of v1.2.1 when
.git
directory not copied.The text was updated successfully, but these errors were encountered: