[Insight-users] RE: Build example problems : ALL_BUILD is not an executable.

[Luis Ibanez]

Hi Steven,


This is a very common mistake.


If you look at the projects in your VisualStudio
workspace, you will see a project called

     "ALL_BUILD"

and then, other projects below this one.

Right now, you have selected this project
as the default project to be built in this
workspace.

This "ALL_BUILD" project is provided for your
convenience, with the goal of aggregating all
the other projects and allow you to build all
of them by simply asking to build the project
"ALL_BUILD". This is the equivalent of the
"all" target in a classical Unix Makefile.
This is quite useful in the case of the Insight
and InsightApplications since we can easily have
50 to 100 projects in the same workspace.

Because this ALL_BUILD is just a dummy target,
it doesn't have any executable associated with
it. So, if you try to execute it... well, you
get the error message that you posted.

 > "Please specify the executable file for
 >  the debug session
 >  Executable file name(browser): "


---

The solution is quite simple:

    Right-click on any of the other projects
    in the workspace and select it as "default"
    project. Then you will be able to run the
    executable from the VisualStudio IDE.


----


Regards,



    Luis



-------------------
Chen,Steven wrote:

> Hi, all
>  
> I follow the ITKsoftwareGuide, and create a new project with ITK. That 
> is CMakeLists.txt and HelloWorld.cxx. I use CMake to build them. And 
> then i load HelloWorld.dsw and built it under VS6. When i execute it, 
> the following error messages always occur:
>  
> */  ONe or more files are out of date or donot exist./*
> */These files need to be built:
> .\All_Build_force_1/*
> */Would you like to build them?/*
> // 
> If i click OK, then the following message will appear:
> *Please specify the executable file for the debug session
> Executable file name(browser):
> *
> So i wonder what is wrong with this?
>  
> Your answer is greatly appreciated.
>  
> Thank you
>  
> Steven Chen
>  
>