View Issue Details

IDProjectCategoryView StatusLast Update
0002293Slicer4Core: Building (CMake, Superbuild)public2012-07-06 12:24
Reporterblowekamp Assigned Tojcfr  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Product VersionSlicer 4.1.1 
Target VersionSlicer 4.2.0Fixed in VersionSlicer 4.2.0 
Summary0002293: Enable external extension to be built with the Slicer proper
Description

My goal it to be able to package Slicer along with my extension in a nice little apple .app bundle.

I would would be good to be able to set a CMake variable in the Slicer3D build to point to my extensions where, it would get included as if it was part of Slicer3D. That would make building, and packaging a customize slicer much easier.

Additional Information

On Jul 2, 2012, at 4:21 PM, Jean-Christophe Fillion-Robin wrote:

Hi Brad,

That could be possible, the idea would be to have a Slicer_EXTENSION_SOURCE_DIRS advacned options that the developer could set to be a list of extensions source dirs.

Then, when building (and then packaging) Slicer, the modules associated with the extensions would be automatically built (and then bundled) within the Slicer package.

That's why the "if(NOT Slicer_SOURCE_DIR)" statements play their role.

Please, create an issue on Slicer tracker.

Hth
Jc

On Mon, Jul 2, 2012 at 4:03 PM, Bradley Lowekamp <blowekamp@mail.nih.gov> wrote:
Hello,

I wish to install a customized slicer with ITKv4 and SimpleITK on a networked drive with my custom extensions.

I have read the documentation here:
http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Versioning#How_to_create_a_Slicer_package

So with the latest changes I am able to package Slicer just fine. The problem comes with the extension(s)...

When I launch the installed Slicer I want the extension to be there, for any user. I am not really sure the best way to do this. As I will likely have different versions of Slicer and different versions of my extension, I need to some how configure each versioned Slicer.app to use my extension. Ideally, I'd like my extension to become part of the .app, for easy portablility. It's apple-like to be able to just drag the .app around ( say off to your laptop ) and have it just work.

I have had some success, by running "make package" in my extension. Then manually mounting the dmg, and copying the files to the internal of the Slicer.app. This seems to work, but it's a little manual and error prone.

I am now wondering if there is a place in the Slicer source tree I could clone my Extension into, and have Slicer just pick it up and build my Extension with Slicer, kind of like the ITK's Modules/External directory. This would make things easier, one build, one make package.

Is there a better way to accomplish this? I just want a .app which contains my Extension.

Thanks,
Brad

========================================================
Bradley Lowekamp
Medical Science and Computing for
Office of High Performance Computing and Communications
National Library of Medicine
blowekamp@mail.nih.gov


slicer-devel mailing list
slicer-devel@bwh.harvard.edu
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel
To unsubscribe: send email to slicer-devel-request@massmail.spl.harvard.edu with unsubscribe as the subject

--
+1 919 869 8849

TagsNo tags attached.

Activities

jcfr

jcfr

2012-07-05 14:46

administrator   ~0005079

Fixed in r20576
See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&amp;revision=20576

blowekamp

blowekamp

2012-07-06 12:24

developer   ~0005105

Great!

I was able to build and create a package simple by defining Slicer_EXTENSION_SOURCE_DIRS to cmake.

Work fine the first time for me!

Issue History

Date Modified Username Field Change
2012-07-03 10:25 blowekamp New Issue
2012-07-03 10:25 blowekamp Status new => assigned
2012-07-03 10:25 blowekamp Assigned To => jcfr
2012-07-03 10:31 jcfr Assigned To jcfr => crmullin
2012-07-03 10:31 jcfr Target Version => Slicer 4.2.0 - Sept 1st 2012
2012-07-03 10:31 jcfr Additional Information Updated
2012-07-03 10:33 blowekamp Description Updated
2012-07-05 12:20 jcfr Assigned To crmullin => jcfr
2012-07-05 14:46 jcfr Note Added: 0005079
2012-07-05 14:46 jcfr Status assigned => resolved
2012-07-05 14:46 jcfr Fixed in Version => Slicer 4.2.0 - Sept 1st 2012
2012-07-05 14:46 jcfr Resolution open => fixed
2012-07-06 12:24 blowekamp Note Added: 0005105
2012-07-06 12:24 blowekamp Status resolved => closed