[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Launch configurations and recognizing executables
|
Great question. This decision was made a long time ago and I'm not sure the people who decided are still around. There was a time when you weren't even allowed to use an executable outside of your workspace which made testing DLLs impossible. But, yeah, scripts would be another one that would be useful.
In general there is a problem that the CDT doesn't separate out the binary as the thing your run versus the thing you get symbols from, which is problematic for embedded where you usually run a stripped version of the executable.
I'm not sure we've fixed this in the DSF launches?
On Mon, Oct 5, 2009 at 11:01 AM, Greg Watson
<g.watson@xxxxxxxxxxxx> wrote:
Hi all,
Anyone who has upgraded to Snow Leopard has probably discovered that it now defaults to 64-bit executables, but these are not recognized by the Mach-O parser. Unfortunately it is now impossible to run a 64-bit program from CDT.
A fix for this is in the works, but it raises a bigger question in my mind. Why can't I put whatever I like in the run configuration, as long as it is executable? What if I want to run a script that invokes my program, for example? It is very annoying behavior to be told that I can't run a program, even though I know I can.
Greg
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
