%% Alain Magloire [EMAIL PROTECTED] writes:
where do you go when the user asks to go to install?
am Ho! I do not know. But it should not matter, we parse the
am makefile and provide the users with a list of the targets. In
am your example should not the install targets be consider as
Bonjour
am (1) (2)
am I've dealt with those a little differently: by providing in the
am IDE a Makefile Editor that understands GNU peculiar(really
am peculiar/inconsistent 8-) syntax, it provides:
There's nothing about GNU make syntax that's more peculiar or
inconsistent than
%% Alain Magloire [EMAIL PROTECTED] writes:
am It looks like a Class View, the widget is a tree, that shows the
am directives of the makefile, it turns out to be practical, for
am makefile browsing etc .. select a node it position the editor
am cursor at the right place, future could do
am It looks like a Class View, the widget is a tree, that shows the
am directives of the makefile, it turns out to be practical, for
am makefile browsing etc .. select a node it position the editor
am cursor at the right place, future could do some quick action, like
am shows the
Bonjour
Integrating make as the underlying engine ... is not easy 8-)
For example to do a real Progress monitor, meaning
how to provide feedback to the users on how many commands done so far and how many
left ?
How to extract information from make, i.e. make has all sort of
am For example to do a real Progress monitor, meaning how to provide
am feedback to the users on how many commands done so far and how
am many left ?
First, make can't tell you how many commands are left because it doesn't
know. This came up a few weeks ago. The way make works is it
