URL: http://scirun.org
GitHub URL: https://github.com/SCIInstitute/SCIRun
The GitHub project is SCIRun 5, a complete rewrite of the GUI front end and graphical components of SCIRun 4, including a more stable and efficient middle layer, with support for Python scripting.
Used as the base for BioMesh, Forward/Inverse and BrainStimulator
Build Notes: http://sciinstitute.github.io/scirun.pages/build.html
I'll try to create a RPM. Please, assigne this ticket.
Thanks @sagitter. I've also add you to the pagure group (I forgot when I added you to the FAS group---sorry about that). You should now be able to create/edit tickets and push to the repo.
Metadata Update from @ankursinha: - Issue untagged with: S: Needs packaging - Issue assigned to sagitter - Issue tagged with: S: WIP
SCIRun automatically downloads and builds many libraries already included on Fedora (freetype, zlib, libpng, boost, ...), i doubt it can be packaged for Fedora in this condition.
Ugh :disappointed:
Does the build system have any options to use system libraries by any chance? Otherwise maybe it can be patched to use the system libraries?
I usually work on patching it up and file an issue upstream discussing the use of system libraries.
What do you think?
Ugh 😞 Does the build system have any options to use system libraries by any chance? Otherwise maybe it can be patched to use the system libraries?
No.
I usually work on patching it up and file an issue upstream discussing the use of system libraries. What do you think?
There is a lot of patching work. I'm asking at upstream level: https://github.com/SCIInstitute/SCIRun/issues/1862
Ah, let's hope upstream is willing to help us out here :pray:
I've also invited you to the Github NeuroFedora organisation.
Please use the various tags in tickets. Helps to keep track of progress :)
Metadata Update from @ankursinha: - Issue tagged with: S: Waiting on upstream
Metadata Update from @sagitter: - Issue untagged with: S: Waiting on upstream - Issue tagged with: S: Needs packaging
Metadata Update from @sagitter: - Assignee reset
Upstream response:
In general, it is preferable from our point of view to build against library versions that we control since we have to support a broad range of platforms (Windows, Mac OS X and different Linux distributions). Including specific versions of third-party libraries allows us to maintain stable Seg3D builds across multiple platforms with the least amount of effort and cost.
I'm sure we all understand their reasoning---but that doesn't necessarily mean using outdated versions of software. If they bundle newest versions of libraries, we can still work with that.
I agree that this is going to be a hard one, so we leave it for later.
Metadata Update from @ankursinha: - Issue untagged with: D: Normal, S: WIP - Issue priority set to: Low (was: Normal) - Issue tagged with: D: Hard, S: On hold
Login to comment on this ticket.