search

Slicer / ExtensionsIndex

Slicer extensions index
https://github.com/Slicer/ExtensionsIndex/#slicer-extensions-index
65 stars 240 forks source link

XNATSlicer - Add extension #194

Closed skumar221 closed 11 years ago

skumar221 commented 11 years ago

Description: Secure File IO with any XNAT server. Win64 for now.

Wiki: http://www.slicer.org/slicerWiki/index.php/Documentation/4.2/Extensions/XNATSlicer

jcfr commented 11 years ago

Hi Sunil,

Thanks for contributing :+1:

To add an extension to the index, it should be available for at least: Linux, MacOSX and Windows. In addition to 4.2, make also sure to submit extension built against slicer nightly. See:

fedorov commented 11 years ago

Sunil, how about you provide detailed instructions on the extension wiki page how it should be compiled/installed on Win64, before you figure out packaging issues on other platforms?

skumar221 commented 11 years ago

Definitely. You'll see it on the wiki within the week.

skumar221 commented 11 years ago

Hi JC,

I'll thank you in advance here because I'm going to bug you a little bit :)

I'm confused as to where to go next. The extension I'm trying to package is a scripted module. When you say "submit extension built against slicer nightly," can you explain this process further and also the necessity of it?

My assumption here is that by pushing my .s4ext to the ExtensionsIndex I've given the Extension Manager all of the info it needs. I take it this is incorrect?

Sunil

pieper commented 11 years ago

By the way Jc: we (Dan Marcus and I) asked Sunil to go ahead with the Extension process even though his work is not yet supported on linux and mac -- the reasoning was that many of the potential users will be on windows and we didn't want to make them wait while the issues are sorted out for the other platforms. Plus, once they start demanding this extension for the other platforms it will be a reminder for us to figure out all the OpenSSL issues :)

-Steve

On Mon, Feb 4, 2013 at 3:25 PM, sunilk-wustl notifications@github.comwrote:

Hi JC,

I'll thank you in advance here because I'm going to bug you a little bit :)

I'm confused as to where to go next. The extension I'm trying to package is a scripted module. When you say "submit extension built against slicer nightly," can you explain this process further and also the necessity of it?

My assumption here is that by pushing my .s4ext to the ExtensionsIndex I've given the Extension Manager all of the info it needs. I take it this is incorrect?

Sunil

— Reply to this email directly or view it on GitHubhttps://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13097325.

jcfr commented 11 years ago

@pieper: Sounds good. That side, as mention @fedorov, more details should be provided.

Hi Sunil,

I updated the documentation to clarify things. See http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions#Contribute_an_extension_description_file

Let me know if you still have questions.

Hth Jc

On Mon, Feb 4, 2013 at 4:01 PM, Steve Pieper notifications@github.comwrote:

By the way Jc: we (Dan Marcus and I) asked Sunil to go ahead with the Extension process even though his work is not yet supported on linux and mac -- the reasoning was that many of the potential users will be on windows and we didn't want to make them wait while the issues are sorted out for the other platforms. Plus, once they start demanding this extension for the other platforms it will be a reminder for us to figure out all the OpenSSL issues :)

-Steve

On Mon, Feb 4, 2013 at 3:25 PM, sunilk-wustl notifications@github.comwrote:

Hi JC,

I'll thank you in advance here because I'm going to bug you a little bit :)

I'm confused as to where to go next. The extension I'm trying to package is a scripted module. When you say "submit extension built against slicer nightly," can you explain this process further and also the necessity of it?

My assumption here is that by pushing my .s4ext to the ExtensionsIndex I've given the Extension Manager all of the info it needs. I take it this is incorrect?

Sunil

— Reply to this email directly or view it on GitHub< https://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13097325>.

— Reply to this email directly or view it on GitHubhttps://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13099147.

+1 919 869 8849

skumar221 commented 11 years ago

Hi JC,

That did clarify things. Thanks. Just to review, here's what I understand needs to happen (please let me know where I'm wrong):

1) Fork/update to 4.2 locally. 2) Regenerate the .s4ext file via CMake, instructions here: https://github.com/Slicer/ExtensionsIndex#extension-build-test-package-and-upload-using-experimentalupload-target 3) Build the experimental-upload target, instructions in the above link 4) Push the newly generated .s4ext to the 4.2 ExtensionsIndex 5) Create a pull request on the ExtensionsIndex

The question I have is are these steps needed for scripted modules? If so, why? (I can infer some reasons, but I just want to make sure...)

Thanks again for letting me pester you here -- much appreciated.

Sunil

jcfr commented 11 years ago

Hi Sunil,

Steps are the same independently of the type of module bundled within an extension.

I consolidated the different FAQ pages of the wiki, would be great if you could update the following page by adding the question and the associated answer.

See http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ/Extensions

There is also a FAQ link available from the developer page: http://www.slicer.org/slicerWiki/index.php?title=Documentation/Nightly/Developers

Thanks Jc

On Mon, Feb 4, 2013 at 9:21 PM, sunilk-wustl notifications@github.comwrote:

Hi JC,

That did clarify things. Thanks. Just to review, here's what I understand needs to happen (please let me know where I'm wrong):

1) Fork/update to 4.2 locally. 2) Regenerate the .s4ext file via CMake, instructions here: https://github.com/Slicer/ExtensionsIndex#extension-build-test-package-and-upload-using-experimentalupload-target 3) Build the experimental-upload target, instructions in the above link 4) Push the newly generated .s4ext to the 4.2 ExtensionsIndex 5) Create a pull request on the ExtensionsIndex

The question I have is are these steps needed for scripted modules? If so, why? (I can infer some reasons, but I just want to make sure...)

Thanks again for letting me pester you here -- much appreciated.

Sunil

— Reply to this email directly or view it on GitHubhttps://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13111502.

+1 919 869 8849

skumar221 commented 11 years ago

Hi JC,

I've spent the last few days trying to accomplish this. I'm having issues with the following step:

"Regenerate the .s4ext file by configuring your extension with CMake see https://github.com/Slicer/ExtensionsIndex#build-your-own-set-of-extensions-against-slicer-trunk-build-tree

I can configure/generate/build OK with cmake-gui+VS2008, but no new *.s4ext files are created. There are other files that get created, just nothing with the ".s4ext" extension. My questions are as follows:

1) Would a scripted module warrant a regenerated .s4ext?
2) Where should I be looking for the regenerated .s4ext? (It's not in the C:\path\to\customExtensions or the C:\path\to\customExtensions-build folders...)

Thanks in advance, Sunil

jcfr commented 11 years ago

Hi Sunil,

The line that trigger the generation of the extension description file is the one reported in [1]

You should also see an output similar to the following one:

[...]

Configuring Scripted module: ScriptedLoadableExtensionTemplate -- Extension description has been written to: /home/kitware/Dashboards/Nightly/SlicerExtensions-build-64bits-QT4.7.4-PythonQt-With-Tcl-CLI-Release-nightly-Testing-master/ScriptedLoadableExtensionTemplate-build/ScriptedLoadableExtensionTemplate.s4ext -- Configuring done

[...]

See [2] for an example.

Hth Jc

[1] https://github.com/Slicer/Slicer/blob/master/Extensions/Testing/ScriptedLoadableExtensionTemplate/CMakeLists.txt#L51 [2] http://slicer.cdash.org/buildSummary.php?buildid=63851

On Mon, Feb 11, 2013 at 3:22 PM, sunilk-wustl notifications@github.comwrote:

Hi JC,

I've spent the last few days trying to accomplish this. I'm having issues with the following step:

"Regenerate the .s4ext file by configuring your extension with CMake see https://github.com/Slicer/ExtensionsIndex#build-your-own-set-of-extensions-against-slicer-trunk-build-tree

I can configure/generate/build OK with cmake-gui+VS2008, but no new *.s4ext files are created. There are other files that get created, just nothing with the ".s4ext" extension. My questions are as follows:

1) Would a scripted module warrant a regenerated .s4ext?

2) Where should I be looking for the regenerated .s4ext? (It's not in the C:\path\to\customExtensions or the C:\path\to\customExtensions-build folders...)

Thanks in advance, Sunil

— Reply to this email directly or view it on GitHubhttps://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13400515.

+1 919 869 8849

skumar221 commented 11 years ago

Hi JC,

I don't see a newly generated .s4ext file or a "Extension description has been written to:" line.

Here's how my extension directory is organized:

C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/ <-- custom .s4ext file C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld <-- cmake build folder

Here's my cmake command-line output. As a side note, I previously used cmake-gui, but it appears to be no different:

-sh-4.1$ cmake -DSlicer_DIR:PATH=C:/Users/skumar01/Desktop/Slicer-build/Slicer-build -DSlicer_EXTENSION_DESCRIPTION_DIR:PATH=C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom -DCMAKE_BUILD_TYPE:STRING=Release C:/Users/skumar01/Desktop/slb/Slicer/Extensions/CMake -- Building for: Visual Studio 9 2008 -- The C compiler identification is MSVC 15.0.30729.1 -- The CXX compiler identification is MSVC 15.0.30729.1 -- Check for working C compiler using: Visual Studio 9 2008 -- Check for working C compiler using: Visual Studio 9 2008 -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler using: Visual Studio 9 2008 -- Check for working CXX compiler using: Visual Studio 9 2008 -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found PythonLibs: C:/Users/skumar01/Desktop/Slicer-build/python-build/PCbuild/amd64/python26.lib -- Found PythonInterp: C:/Users/skumar01/Desktop/Slicer-build/python-build/PCbuild/amd64/python.exe (found version "2.6.6") -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - not found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - found -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found -- Found Qt4: C:/qt/bin/qmake.exe (found version "4.7.4") -- Configuring SlicerExtensions with Qt 4.7.4 (using modules: CORE, GUI, NETWORK, UITOOLS, XML, WEBKIT, SVG, SQL, SCRIPT, TEST, ) -- Found Git: C:/Program Files (x86)/Git/cmd/git.exe -- Found Subversion: C:/Program Files (x86)/SlikSvn/bin/svn.exe -- Extension:C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/XNATSlicer.s4ext -- Configuring extension: XNATSlicer -- Configuring done -- Generating done -- Build files have been written to: C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld

jcfr commented 11 years ago

For some reason, the description is not properly printed .. but looking at your output:

-- Extension:C:/Users/skumar01/Desktop/XNATSlicerWiki/ ExtensionsIndex/Custom/XNATSlicer.s4ext

Hth Jc

On Mon, Feb 11, 2013 at 5:06 PM, sunilk-wustl notifications@github.comwrote:

Hi JC,

I don't see a newly generated .s4ext file or a "Extension description has been written to:" line.

Here's how my extension directory is organized:

C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/ <-- custom .s4ext file C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld <-- cmake build folder

Here's my cmake command-line output. As a side note, I previously used cmake-gui, but it appears to be no different:

-sh-4.1$ cmake -DSlicer_DIR:PATH=C:/Users/skumar01/Desktop/Slicer-build/Slicer-build -DSlicer_EXTENSION_DESCRIPTION_DIR:PATH=C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom -DCMAKE_BUILD_TYPE:STRING=Release C:/Users/skumar01/Desktop/slb/Slicer/Extensions/CMake -- Building for: Visual Studio 9 2008 -- The C compiler identification is MSVC 15.0.30729.1 -- The CXX compiler identification is MSVC 15.0.30729.1 -- Check for working C compiler using: Visual Studio 9 2008 -- Check for working C compiler using: Visual Studio 9 2008 -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler using: Visual Studio 9 2008 -- Check for working CXX compiler using: Visual Studio 9 2008 -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found PythonLibs: C:/Users/skumar01/Desktop/Slicer-build/python-build/PCbuild/amd64/python26.lib -- Found PythonInterp: C:/Users/skumar01/Desktop/Slicer-build/python-build/PCbuild/amd64/python.exe (found version "2.6.6") -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - not found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - found -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found -- Found Qt4: C:/qt/bin/qmake.exe (found version "4.7.4") -- Configuring SlicerExtensions with Qt 4.7.4 (using modules: CORE, GUI, NETWORK, UITOOLS, XML, WEBKIT, SVG, SQL, SCRIPT, TEST, ) -- Found Git: C:/Program Files (x86)/Git/cmd/git.exe

-- Found Subversion: C:/Program Files (x86)/SlikSvn/bin/svn.exe

Extension:C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/XNATSlicer.s4ext -- Configuring extension: XNATSlicer -- Configuring done -- Generating done -- Build files have been written to: C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld

— Reply to this email directly or view it on GitHubhttps://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13406038.

+1 919 869 8849

skumar221 commented 11 years ago

That's the original .s4ext file that I point cmake to, not the newly generated one. I'm guessing the new one should be in C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld, right? The timestamp on the file also confirms it hasn't been touched -- would cmake overwrite these files?

jcfr commented 11 years ago

Hi Sunil,

There are two concepts:

1) Developing an extension and generating the associated extension description file:

    - An extension description file will be generated in the build tree

of an extension each time it is configured. The output of the configuration process of any given extension should display where the associated description file has been generated.

    Assuming you develop extension Foo, you would have the following

structure:

 /path/to/Projects/Foo
 /path/to/Projects/Foo-build     #<--- where s4ext will be generated

2) Building one or multiple extensions using an existing set of description files

    - This is done by following

https://github.com/Slicer/ExtensionsIndex#build-your-own-set-of-extensions-against-slicer-trunk-build-tree (Implicitly, each extension will also be configured .. and as a by-product an extension description file will be also generated ...)

  Example of directory structure corresponding to an extension index

having to extensions: Foo and Bar

          /path/to/Projects/MyExtensionsIndex/Foo.s4ext
          /path/to/Projects/MyExtensionsIndex/Bar.s4ext
          /path/to/Projects/MyExtensionsIndex-build/Foo
          /path/to/Projects/MyExtensionsIndex-build/Foo-build  #<---

where s4ext will be implictly generated /path/to/Projects/MyExtensionsIndex-build/Bar /path/to/Projects/MyExtensionsIndex-build/Bar-build #<--- where s4ext will be implictly generated

Let me know if you have any other questions.

Also agree the documentation is confusion, will be working on it in the coming days by consolidating everything into the wiki. (instead of having doc on github and on the wiki ..)

Thanks Jc

On Mon, Feb 11, 2013 at 5:29 PM, sunilk-wustl notifications@github.comwrote:

That's the original .s4ext file that I point cmake to, not the newly generated one. I'm guessing the new one should be in C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld, right? The timestamp on the file also confirms it hasn't been touched -- would cmake overwrite these files?

— Reply to this email directly or view it on GitHubhttps://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13407202.

+1 919 869 8849

skumar221 commented 11 years ago

Hi JC,

What I'm saying is that I'm following process (1), but it doesn't look like it works. At least in Windows.

For instance, I'm not getting any *.s4ext in the /path/to/Projects/Foo-build folder (for me, this is: C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld). Furthermore, the cmake output I posted above also shows that it doesn't create any new .s4ext file. (A VS2008 solution gets built fine, however.)

Any ideas, or could this be a potential bug?

-Sunil

jcfr commented 11 years ago

The log reported above is specific to process (2) since you were building an extension index. Anyway, as explained, if you look inside the folder:

C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld/SlicerXNAT-build

After building the index, you should see that a description file has been "implicitly" generated. In this case, the generated description file should be the same has the one already existing in the folder C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/

For information, a template scripted extension is being build every night on VS2008.

If you still have question, I propose you join tomorrow hangout :+1:

skumar221 commented 11 years ago

Hi JC,

I want thank you again for fielding my questions. It's greatly appreciated especially knowing how involved you are in all aspects of Slicer. I'm definitely interested in the hangout, though of all times I can't attend today's (assuming it's still at 4pm EST.)

Going back to the thread, when you say: "After building the index, you should see that a description file has been "implicitly" generated. In this case, the generated description file should be the same has the one already existing in the folder..."

do you mean there should be a new .s4ext file somewhere within the build path:

C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld/XNATSlicer-build

or is it the same XNATSlicer.s4ext file found in:

C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/

?

Below is a list of the files in the build directory:

C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld/XNATSlicer-build

Notice there's nothing in the way of an .s4ext -- a file search verifies this. Again, everything builds OK. 

-sh-4.1$ pwd
/cygdrive/c/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld/XNATSlicer-build
-sh-4.1$ ls -Rl
.:
total 220
-rwx------+ 1 skumar01 mkpasswd 77192 Feb 12 11:17 ALL_BUILD.vcproj
-rwx------+ 1 skumar01 mkpasswd 76938 Feb 12 11:17 CMakeCache.txt
drwx------+ 1 skumar01 mkpasswd     0 Feb 12 11:17 CMakeFiles
-rwx------+ 1 skumar01 mkpasswd  2022 Feb 12 11:17 SlicerExtensions.sln
-rwx------+ 1 skumar01 mkpasswd 56001 Feb 12 11:17 ZERO_CHECK.vcproj
-rwx------+ 1 skumar01 mkpasswd  1651 Feb 12 11:17 cmake_install.cmake

./CMakeFiles:
total 50
drwx------+ 1 skumar01 mkpasswd     0 Feb 12 11:17 2.8.10.2
-rwx------+ 1 skumar01 mkpasswd    45 Feb 12 11:17 ALL_BUILD.rule
-rwx------+ 1 skumar01 mkpasswd  5304 Feb 12 11:17 CMakeError.log
-rwx------+ 1 skumar01 mkpasswd 11625 Feb 12 11:17 CMakeOutput.log
drwx------+ 1 skumar01 mkpasswd     0 Feb 12 11:17 CMakeTmp
-rwx------+ 1 skumar01 mkpasswd   223 Feb 12 11:17 TargetDirectories.txt
-rwx------+ 1 skumar01 mkpasswd    45 Feb 12 11:17 ZERO_CHECK.rule
-rwx------+ 1 skumar01 mkpasswd    86 Feb 12 11:17 cmake.check_cache
-rwx------+ 1 skumar01 mkpasswd    51 Feb 12 11:17 generate.stamp
-rwx------+ 1 skumar01 mkpasswd 14486 Feb 12 11:17 generate.stamp.depend
-rwx------+ 1 skumar01 mkpasswd   112 Feb 12 11:17 generate.stamp.list

./CMakeFiles/2.8.10.2:
total 90
-rwx------+ 1 skumar01 mkpasswd  1457 Feb 12 11:17 CMakeCCompiler.cmake
-rwx------+ 1 skumar01 mkpasswd  1592 Feb 12 11:17 CMakeCXXCompiler.cmake
-rwx------+ 1 skumar01 mkpasswd 36352 Feb 12 11:17 CMakeDetermineCompilerABI_C.bin
-rwx------+ 1 skumar01 mkpasswd 36352 Feb 12 11:17 CMakeDetermineCompilerABI_CXX.bin
-rwx------+ 1 skumar01 mkpasswd   263 Feb 12 11:17 CMakeRCCompiler.cmake
-rwx------+ 1 skumar01 mkpasswd   363 Feb 12 11:17 CMakeSystem.cmake
drwx------+ 1 skumar01 mkpasswd     0 Feb 12 11:17 CompilerIdC
drwx------+ 1 skumar01 mkpasswd     0 Feb 12 11:17 CompilerIdCXX

./CMakeFiles/2.8.10.2/CompilerIdC:
total 36
-rwx------+ 1 skumar01 mkpasswd 12457 Feb 12 11:17 CMakeCCompilerId.c
-rwx------+ 1 skumar01 mkpasswd 10752 Feb 12 11:17 CompilerIdC.exe
-rwx------+ 1 skumar01 mkpasswd  1352 Feb 12 11:17 CompilerIdC.vcproj
drwx------+ 1 skumar01 mkpasswd     0 Feb 12 11:17 Debug

./CMakeFiles/2.8.10.2/CompilerIdC/Debug:
total 41
-rwx------+ 1 skumar01 mkpasswd  9396 Feb 12 11:17 BuildLog.htm
-rwx------+ 1 skumar01 mkpasswd  1869 Feb 12 11:17 CMakeCCompilerId.obj
-rwx------+ 1 skumar01 mkpasswd   623 Feb 12 11:17 CompilerIdC.exe.intermediate.manifest
-rwx------+ 1 skumar01 mkpasswd    66 Feb 12 11:17 mt.dep
-rwx------+ 1 skumar01 mkpasswd 19456 Feb 12 11:17 vc90.idb

./CMakeFiles/2.8.10.2/CompilerIdCXX:
total 32
-rwx------+ 1 skumar01 mkpasswd 12185 Feb 12 11:17 CMakeCXXCompilerId.cpp
-rwx------+ 1 skumar01 mkpasswd 10752 Feb 12 11:17 CompilerIdCXX.exe
-rwx------+ 1 skumar01 mkpasswd  1362 Feb 12 11:17 CompilerIdCXX.vcproj
drwx------+ 1 skumar01 mkpasswd     0 Feb 12 11:17 Debug

./CMakeFiles/2.8.10.2/CompilerIdCXX/Debug:
total 41
-rwx------+ 1 skumar01 mkpasswd  9492 Feb 12 11:17 BuildLog.htm
-rwx------+ 1 skumar01 mkpasswd  1873 Feb 12 11:17 CMakeCXXCompilerId.obj
-rwx------+ 1 skumar01 mkpasswd   623 Feb 12 11:17 CompilerIdCXX.exe.intermediate.manifest
-rwx------+ 1 skumar01 mkpasswd    66 Feb 12 11:17 mt.dep
-rwx------+ 1 skumar01 mkpasswd 19456 Feb 12 11:17 vc90.idb

./CMakeFiles/CMakeTmp:
total 0

Thanks again here, Sunil

jcfr commented 11 years ago

Hi Sunil,

Given this new input, I am assuming you manually created the original s4ext files and the following line is missing from your CMakeLists.txt:

include(${Slicer_EXTENSION_CPACK})

See here for an example: https://github.com/Slicer/Slicer/blob/master/Extensions/Testing/ScriptedLoadableExtensionTemplate/CMakeLists.txt#L51

Hth Jc

On Tue, Feb 12, 2013 at 12:57 PM, sunilk-wustl notifications@github.comwrote:

Hi JC,

I want thank you again for fielding my questions. It's greatly appreciated especially knowing how involved you are in all aspects of Slicer. I'm definitely interested in the hangout, though of all times I can't attend today's (assuming it's still at 4pm EST.)

Going back to the thread, when you say: "After building the index, you should see that a description file has been "implicitly" generated. In this case, the generated description file should be the same has the one already existing in the folder..."

do you mean there should be a new .s4ext file somewhere within the build path:

C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld/XNATSlicer-build or is it the same XNATSlicer.s4ext file found in: C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/ ?

Below is a list of the files in the build directory: C:/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld/XNATSlicer-build

Notice there's nothing in the way of an .s4ext -- a file search verifies this. Again, everything builds OK.

-sh-4.1$ pwd /cygdrive/c/Users/skumar01/Desktop/XNATSlicerWiki/ExtensionsIndex/Custom/bld/XNATSlicer-build -sh-4.1$ ls -Rl .: total 220 -rwx------+ 1 skumar01 mkpasswd 77192 Feb 12 11:17 ALL_BUILD.vcproj -rwx------+ 1 skumar01 mkpasswd 76938 Feb 12 11:17 CMakeCache.txt drwx------+ 1 skumar01 mkpasswd 0 Feb 12 11:17 CMakeFiles -rwx------+ 1 skumar01 mkpasswd 2022 Feb 12 11:17 SlicerExtensions.sln -rwx------+ 1 skumar01 mkpasswd 56001 Feb 12 11:17 ZERO_CHECK.vcproj -rwx------+ 1 skumar01 mkpasswd 1651 Feb 12 11:17 cmake_install.cmake

./CMakeFiles: total 50 drwx------+ 1 skumar01 mkpasswd 0 Feb 12 11:17 2.8.10.2 -rwx------+ 1 skumar01 mkpasswd 45 Feb 12 11:17 ALL_BUILD.rule -rwx------+ 1 skumar01 mkpasswd 5304 Feb 12 11:17 CMakeError.log -rwx------+ 1 skumar01 mkpasswd 11625 Feb 12 11:17 CMakeOutput.log drwx------+ 1 skumar01 mkpasswd 0 Feb 12 11:17 CMakeTmp -rwx------+ 1 skumar01 mkpasswd 223 Feb 12 11:17 TargetDirectories.txt -rwx------+ 1 skumar01 mkpasswd 45 Feb 12 11:17 ZERO_CHECK.rule -rwx------+ 1 skumar01 mkpasswd 86 Feb 12 11:17 cmake.check_cache -rwx------+ 1 skumar01 mkpasswd 51 Feb 12 11:17 generate.stamp -rwx------+ 1 skumar01 mkpasswd 14486 Feb 12 11:17 generate.stamp.depend -rwx------+ 1 skumar01 mkpasswd 112 Feb 12 11:17 generate.stamp.list

./CMakeFiles/2.8.10.2: total 90 -rwx------+ 1 skumar01 mkpasswd 1457 Feb 12 11:17 CMakeCCompiler.cmake -rwx------+ 1 skumar01 mkpasswd 1592 Feb 12 11:17 CMakeCXXCompiler.cmake -rwx------+ 1 skumar01 mkpasswd 36352 Feb 12 11:17 CMakeDetermineCompilerABI_C.bin -rwx------+ 1 skumar01 mkpasswd 36352 Feb 12 11:17 CMakeDetermineCompilerABI_CXX.bin -rwx------+ 1 skumar01 mkpasswd 263 Feb 12 11:17 CMakeRCCompiler.cmake -rwx------+ 1 skumar01 mkpasswd 363 Feb 12 11:17 CMakeSystem.cmake drwx------+ 1 skumar01 mkpasswd 0 Feb 12 11:17 CompilerIdC drwx------+ 1 skumar01 mkpasswd 0 Feb 12 11:17 CompilerIdCXX

./CMakeFiles/2.8.10.2/CompilerIdC: total 36 -rwx------+ 1 skumar01 mkpasswd 12457 Feb 12 11:17 CMakeCCompilerId.c -rwx------+ 1 skumar01 mkpasswd 10752 Feb 12 11:17 CompilerIdC.exe -rwx------+ 1 skumar01 mkpasswd 1352 Feb 12 11:17 CompilerIdC.vcproj drwx------+ 1 skumar01 mkpasswd 0 Feb 12 11:17 Debug

./CMakeFiles/2.8.10.2/CompilerIdC/Debug: total 41 -rwx------+ 1 skumar01 mkpasswd 9396 Feb 12 11:17 BuildLog.htm -rwx------+ 1 skumar01 mkpasswd 1869 Feb 12 11:17 CMakeCCompilerId.obj -rwx------+ 1 skumar01 mkpasswd 623 Feb 12 11:17 CompilerIdC.exe.intermediate.manifest -rwx------+ 1 skumar01 mkpasswd 66 Feb 12 11:17 mt.dep -rwx------+ 1 skumar01 mkpasswd 19456 Feb 12 11:17 vc90.idb

./CMakeFiles/2.8.10.2/CompilerIdCXX: total 32 -rwx------+ 1 skumar01 mkpasswd 12185 Feb 12 11:17 CMakeCXXCompilerId.cpp -rwx------+ 1 skumar01 mkpasswd 10752 Feb 12 11:17 CompilerIdCXX.exe -rwx------+ 1 skumar01 mkpasswd 1362 Feb 12 11:17 CompilerIdCXX.vcproj drwx------+ 1 skumar01 mkpasswd 0 Feb 12 11:17 Debug

./CMakeFiles/2.8.10.2/CompilerIdCXX/Debug: total 41 -rwx------+ 1 skumar01 mkpasswd 9492 Feb 12 11:17 BuildLog.htm -rwx------+ 1 skumar01 mkpasswd 1873 Feb 12 11:17 CMakeCXXCompilerId.obj -rwx------+ 1 skumar01 mkpasswd 623 Feb 12 11:17 CompilerIdCXX.exe.intermediate.manifest -rwx------+ 1 skumar01 mkpasswd 66 Feb 12 11:17 mt.dep -rwx------+ 1 skumar01 mkpasswd 19456 Feb 12 11:17 vc90.idb

./CMakeFiles/CMakeTmp: total 0

Thanks again here, Sunil

— Reply to this email directly or view it on GitHubhttps://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13445967.

+1 919 869 8849

skumar221 commented 11 years ago

Hi JC,

It looks like I'm getting a link error when I try and build the .sln file. (I've updated and built Slicer using the latest trunk, also.)

I'm going to move this discussion to the dev mailing list in case others face the same issue.

Thanks again for your help. Talk to you on the dev list!

Sunil

jcfr commented 11 years ago

Sounds good. And make sure to point us to the source code. Thanks Jc

On Wed, Feb 13, 2013 at 11:31 AM, sunilk-wustl notifications@github.comwrote:

Hi JC,

It looks like I'm getting a link error when I try and build the .sln file. (I've updated and built Slicer using the latest trunk, also.)

I'm going to move this discussion to the dev mailing list in case others face the same issue.

Thanks again for your help. Talk to you on the dev list!

Sunil

— Reply to this email directly or view it on GitHubhttps://github.com/Slicer/ExtensionsIndex/issues/194#issuecomment-13503065.

+1 919 869 8849

skumar221 commented 11 years ago

No link errors now. Dah! But still no regenerated .s4ext. Will move to dev list anyway.

jcfr commented 11 years ago

Closing the issue. A pull request will be submitted soon.