Hi again,
I came with some new results:
in order to make an executable file of my version of MITK I did the
following steps:
1. installed NSIS
2. built MITK-superbuild.sln in Release and Debug mode (building the
project ALL_BUILD)
3. did the same for MyProject-superbuild.sln
4. opened by visual the file: startVS_release
5. built the package while the solution configuration is on the release mode
6. That last stage failed with some errors such as:
CMake Error at
A/MITK_myProject-superbuild/MyProject-build/Apps/MyApp/cmake_install.cmake
... file INSTALL cannot find
BUT, a new directory called _CPack_Packages has been generated.
By double click on MyApp.exe in the path the executable is working:
A\MITK_myProject-superbuild\MyProject-build\_CPack_Packages\win32\NSIS\MyProject-0.1.1_rf99582-win32\bin
but it contains only *mine* developed modules, without existing modules of
MITK which I've inserted in the configuration process.
*note that at the configuration process of MyProject, I added a new entry
with the path: B\MITK-superbuild\MITK-build
How can I get an executable which contains all the requested modules (mine
+ mitk's modules)
Any suggestions would be very appreciated.
Regards,
Miri
On Fri, Dec 23, 2011 at 1:15 PM, Goch, Caspar Jonas <
[email protected]> wrote:
> Hi Miri,****
>
> ** **
>
> I assume you are looking for a way to provide people with a handy binary
> of your work. The usual way to achieve this would be by building an
> installer.****
>
> For this you will need to install NSIS ( see also
> http://www.mitk.org/wiki/Deployment ). The installer containing all
> active bundles is later build by building the target PACKAGE.****
>
> ** **
>
> As for your other question, yes you want to build a Release installer .
> Have you done your superbuild both in Release and Debug? As in have you
> compiled the toolkits we use as release as well?****
>
> ** **
>
> Regards,****
>
> Caspar****
>
> ** **
>
> *Von:* Miri Trope [mailto:[email protected]]
> *Gesendet:* Freitag, 23. Dezember 2011 10:31
> *An:* [email protected]
> *Betreff:* [mitk-users] Generating executable file****
>
> ** **
>
> Hi all,****
>
>
> I was wondering how can I generate an executable file of MITK (my version
> of MITK i.e. after I added my modules) and run it on other computer.
> I'm working on windows, visual studio 9.
> I started by double clicking on the MyApp.exe file which is located in the
> path:
>
> A\MITK_myProjects-superbuild\MyProject-build\bin\Debug
>
> But it's asking me to add a lot of DLL files ...
> I guess that there is other elegant way to do that.
>
> *Note that I'd like to get an executable of the release mode because it's
> faster then the debug (am I right?).
> But it returns strange linking errors when I try to compile my application
> on release mode such as:
> 2>LINK : fatal error LNK1181: cannot open input file 'ImageExtraction.lib'
> 3>LINK : fatal error LNK1181: cannot open input file
> 'C:\MITK-root\MITK-superbuild\MITK-build\bin\Release\org_mitk_gui_qt_common.lib'
>
> Thanks in advance for any help.****
>
> ** **
>
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
