>> Thank Ant for the pointer.
>
>You're welcome.
>Let us know if you do use leds.
>
>Ant
>

Well, I've attempted to use it. I'm still trying to set it up so I can compile-run-debug D code. Do you have a sample set up that I can look at?

Vanh

In article <c6p604$1bvt$1@digitaldaemon.com>, Vanh says...
>
>
>
>>> Thank Ant for the pointer.
>>
>>You're welcome.
>>Let us know if you do use leds.
>>
>>Ant
>>
>
>Well, I've attempted to use it.

attempted? hmmm... that doesn't sound good...
you shouldn't be strugling with it
(every thing seems very natural to me...)
leds was suppose to be simple to use :(

> I'm still trying to set it up so I
>can compile-run-debug D code.

wasn't the user manual helpfull? http://leds.sourceforge.net/userManualProj.html

but you should be able to create a new project from the
project view "new" icon or project menu/new.
you just need to:
- enter the project name and directory on the basic,
- enter dmd and phobos location on the build,
- and enter the target definitions
http://leds.sourceforge.net/projTarget.html

don't forget the srcdirs or your project will be empty as far as
the targets are concern (I'll change to empty == all).
And after changing the targets you always need to restart,
is very fast and the internal states are saved so you don't even
notice it;)
I agree that the target definition UI is kind of uggly but
once you done it once...

now, about the debug - it's not supported.
I use DDD with gdb but cannot see the D sources (so it's usefull
only to debug when I interface with C on DUI)

> Do you have a sample set up that I can look at?

Maybe I could ship a leds project definition with the source... Maybe all the definitions for DUI and all the tests.

It would be a question of pointing to the right directories.
A dialog could be popup up when a project doesn't point
to a valid directory. That would be costly in terms of size
or startup time. I'll probably do it.

Ant

What I'm trying to do is to create a console project to run
a sample wc example from D documentation.
here the output message.

*** Executing: cd /home/vphom/D/Test/src ; make -f Makefile.wordc all clean
make: Makefile.wordc: No such file or directory
make: *** No rule to make target `Makefile.wordc'.  Stop.

>wasn't the user manual helpfull? http://leds.sourceforge.net/userManualProj.html
not much, unfortunately.

>but you should be able to create a new project from the
>project view "new" icon or project menu/new.
>you just need to:
>- enter the project name and directory on the basic,
>- enter dmd and phobos location on the build,
>- and enter the target definitions
>http://leds.sourceforge.net/projTarget.html
>
Done that, by the way where is my project files saved to?
How can I reopen myproject?
There's no menu to open my previous project.

>don't forget the srcdirs or your project will be empty as far as
On the project->properties->Targets->srcdirs textbox when I enter the location of source dir it was clear up after I click ok and then reopen it. So I don't know if the source dir is being used.

>now, about the debug - it's not supported.
>I use DDD with gdb but cannot see the D sources (so it's usefull
>only to debug when I interface with C on DUI)
Doesn't D have its own debugger?

>Maybe I could ship a leds project definition with the source... Maybe all the definitions for DUI and all the tests.
>
>It would be a question of pointing to the right directories.
>A dialog could be popup up when a project doesn't point
>to a valid directory. That would be costly in terms of size
>or startup time. I'll probably do it.
Well I think you could fill-in with all the default value, so to get the user up and runing. Then he or she could customized to whatever setting they needed much like kdevelop does.

Vanh

On Thu, 29 Apr 2004 03:47:53 +0000, Vanh wrote:

> What I'm trying to do is to create a console project to run
> a sample wc example from D documentation.
> here the output message.
[...]
> Well I think you could fill-in with all the default value, so to get the user up and runing.

that's a good idea.

 Then he or she could customized to whatever setting
> they needed much like kdevelop does.

ah! kdevelop!
I had answer all your questions step by step then I got
to that line and decided to try kdevelop!

It crashed my X server and I lost then entire post... :)

I'll do a step by step stetup of a simple project and repost it.

Ant

On Thu, 29 Apr 2004 00:10:56 -0400, Ant wrote:

> On Thu, 29 Apr 2004 03:47:53 +0000, Vanh wrote:
> 
>> What I'm trying to do is to create a console project to run
>> a sample wc example from D documentation.
>> here the output message.
> 
> I'll do a step by step setup of a simple project and repost it.

I just uploaded it to the leds pages
I assure you it has the same quality as the other user manual pages :(

check it at:

http://leds.sourceforge.net/howtoCreateProject.html

Ant

>   * enter "obj" on skip dirs
>    * press ok (you don't have to press OK now, you can proceed directly to step >2a)
>     two sub directories on your project base directory:
>         o src
>         o obj
>           the obj directory will not be visible as we instructed the project
>          to skip that directory on the project view.

>if you exit and restart leds the project should still be visible
When I exist and restart the project is not there. And I don't know how to get it back. May be my installation is screw up some how.

Vanh

On Fri, 30 Apr 2004 02:44:18 +0000, Vanh wrote:

> 
> 
>>   * enter "obj" on skip dirs
>>    * press ok (you don't have to press OK now, you can proceed directly to step >2a)
>>     two sub directories on your project base directory:
>>         o src
>>         o obj
>>           the obj directory will not be visible as we instructed the project
>>          to skip that directory on the project view.
> 
>>if you exit and restart leds the project should still be visible
> When I exist and restart the project is not there. And I don't know how to get it back. May be my installation is screw up some how.
> 
> Vanh

check if you have the leds home direcories:
~/.leds
~/.leds_data
~/.leds_data/projects

the project file *.lpj should be in ~/leds_data/projects

leds saves the window size and position and opened files between runs. does it do that on your system? That is on the save on openedFiles.leds and preferences.leds

to create those instructions I run a new install of leds changing the home parameters:

leds --home ~/.ledsDemo --data ~/.ledsDemo_data

leds created the following dir tree:

.ledsDemo
|-- openedFiles.leds
`-- preferences.leds
.ledsDemo_data
`-- projects
    `-- wc.lpj

except wc.lpj that leds created only when the wc project
was created.
(openedFiles.leds and preferences.leds are also
not created when leds first start up)
Other user(s) reported success creating leds projects.

!!!!!!!!! wait I just found a bug !!!!!!!!! :

if the home directory and the data directory are the some the projects subdirectory doesn't get created!!?

did you do that? force home and data to be the same directory? for example

leds --home .leds1 --data .leds1 <<-- will fail to create projects subdir

with no projects subdir the project doesn't get saved!

Ant

On Fri, 30 Apr 2004 02:44:18 +0000, Vanh wrote:

> 
> 
>>   * enter "obj" on skip dirs
>>    * press ok (you don't have to press OK now, you can proceed directly to step >2a)
>>     two sub directories on your project base directory:
>>         o src
>>         o obj
>>           the obj directory will not be visible as we instructed the project
>>          to skip that directory on the project view.
> 
>>if you exit and restart leds the project should still be visible
> When I exist and restart the project is not there. And I don't know how to get it back. May be my installation is screw up some how.
> 
> Vanh

Do you want to chat somewhere?
I not too familiar with that but I do have xchat...

email me, it's on the header of this message.

Ant