Charles wrote:

>>To see what is happening after you compile or Build, the compile string
>>is copied to the Clipboard.
> 
> 
> Ahh cool :).
> 
> Here is the results:
> 
> C:\dmd\bin\dmd.exe -c C:\Projects\JSGenerator\jsgenerator.d -O -inline
> "-I"C:\Documents and Settings\qbert\My
> Documents\Unzipped\DManager\DManager\";C:\dfl"
> 
> Are you planning on a kylix version ?
> 
> Charlie
> 
> "David Medlock" <amedlock@nospam.org> wrote in message
> news:d0so4l$2j7k$1@digitaldaemon.com...
> 
>>Charles wrote:
>>
>>>>Perhaps I am a lone user of Windows here....
>>>
>>>
>>>It would be most useful to me on linux :S, is Kylix free ?
>>>
>>>Quick note , I added a file to a project and clicked 'compile file' ,
> 
> and i
> 
>>>get 'cant read and.d' .  The path includes Documents and Settings , are
> 
> you
> 
>>>qouting the import paths / compile-e files ?
>>>
>>>Same thing when I compile the project.
>>>
>>>Through my own trial and error I've found the linker wont accept spaces
> 
> in
> 
>>>directories even if its quoted, I ended up using GetShortPathName.
>>>
>>>Looks fun though!
>>>
>>>Thanks,
>>>Charles
>>>
>>>
>>>"David Medlock" <amedlock@nospam.org> wrote in message
>>>news:d0seh8$2894$1@digitaldaemon.com...
>>>
>>>
>>>>Attached is DManager Beta 3.
>>>>
>>>>- Added a 'Stay on top option'
>>>>- Added a Build/Run option to projects. It builds an EXE, runs the
>>>>program and captures the output.
>>>>- increased size of error messages in tree view.
>>>>- Fixed a bug where Menu showed Full Build but internally the option
>>>>wasn't set.
>>>>
>>>>
>>>>I am fairly surprised I have only recieved 2 responses to this.
>>>>Its quite useful to me(I haven't written a makefile since I started
>>>>using it), and I am basically asking 'what do you guys want' in it.
>>>>
>>>>Perhaps I am a lone user of Windows here....
>>>>
>>>>For those who do try it, let me know if you find any problems.
>>>>
>>>>-David
>>>>
>>>>email:
>>>>ashleymedlock at yahoo dot com
>>>>
>>>
>>>
>>>
>>Actually it should be quoting them.
>>
>>To see what is happening after you compile or Build, the compile string
>>is copied to the Clipboard.
>>
>>You can paste this into notepad and see whats happening.
>>
>>I will look into it though.
>>
> 
> 

I would like to support Kylix.

I am not Linux savvy, but if anyone has Kylix, let me know and I will send you the source (it will get a refactor before a public release).

A guy at work says he can get me a copy of Kylix 6(?) but I don't have a Linux box. :(

That bug will be fixed next release.

On Fri, 11 Mar 2005 10:51:49 -0800, Marcus IkeaTheSofa wrote:


[snip]

> usually I make an exe with this command:
> dmd helloworld.d dfl.lib -L/exet:nt/su:windows:4.0

I usually make an exe with this command:

build helloworld

-- 
Derek Parnell
Melbourne, Australia
http://www.dsource.org/projects/build
12/03/2005 8:16:04 AM

Marcus IkeaTheSofa wrote:
> 
> Last time you posted your tool I downloaded it and was going to try it but my harddrive went down and I had to reinstall everything.. Long story short, I just downloaded your tool and was messing around with it a little bit. I haven't figured out how to get it to work with dfl yet.
> usually I make an exe with this command:
> dmd helloworld.d dfl.lib -L/exet:nt/su:windows:4.0
> I found where you can pass flags to the linker but you only have check boxs for DMD. I think this is a great tool. I'm a novice programmer but I think this will be really useful.

What you do is Right click a project, go to settings, then click the Linker Flags button. Add the Line

/exet:nt/su:windows:4.0

and you should be good.

Walter wrote:
> "David Medlock" <amedlock@nospam.org> wrote in message
> news:d0seh8$2894$1@digitaldaemon.com...
> 
>>Attached is DManager Beta 3.
> 
> 
> Great! I think you'd get more responses, though, if the file was hosted on a
> website and an ftp link is provided here. Otherwise, the message here will
> scroll up and be overlooked after a few days.

David,

You can get a free webspace from many different sources. Personally, I have both a geocities.com and a tripod.com website. There is a limit to the bandwidth (and server space), but I wouldn't expect it to be much of a problem for you unless your program grows in size a lot.

Alternatively, you could just upload it to the D_Lab Yahoo! group (http://groups.yahoo.com/group/d_lab/).

Then, you could put a link to your website somewhere in the wiki, maybe the ReferenceForTools page (http://www.prowiki.org/wiki4d/wiki.cgi?ReferenceForTools).

-- 
Justin (a/k/a jcc7)
http://jcc_7.tripod.com/d/

Great work!

It is better to provide an option to specify libraries while linking.

Thanks!

Altair_liu@hotmail.com wrote:
> Great work!
> 
> It is better to provide an option to specify libraries while linking.
> 
> Thanks! 
> 
> 
Yes this is one of my 'todos'.

Currently you can still browse to \dm\lib\ and add the lib files themselves, though I would like them to be presented when you configure your project.

I don't know if I should just

1 - look in \dmd\lib;..\dm\lib and display that list, or
2 - let the user specify the lib location in workspace settings, or
3 - look for lib files specified in linker options

#3 is probably the best choice.  If a '.lib' is specified in linker options then I will just pass it on the the link process.

David Medlock says...
>
>Altair_liu@hotmail.com wrote:
>> Great work!
>> 
>> It is better to provide an option to specify libraries while linking.
>> 
>> Thanks!
>> 
>> 
>Yes this is one of my 'todos'.
>
>Currently you can still browse to \dm\lib\ and add the lib files themselves, though I would like them to be presented when you configure your project.
>
>I don't know if I should just
>
>1 - look in \dmd\lib;..\dm\lib and display that list, or
>2 - let the user specify the lib location in workspace settings, or
>3 - look for lib files specified in linker options
>
>#3 is probably the best choice.  If a '.lib' is specified in linker options then I will just pass it on the the link process.

Wait, here is a thought:
1.  allow the user to set the lib locations
2.  allow the user have the option to say "only look in the user's set lib
locations'
3.  if option 2 is off, then look also on \dmd\lib;...\dm\lib

That way everything is cover and later you won't have to add option 2. ;-)

josé

"David Medlock" <amedlock@nospam.com> wrote:

>
> 1 - look in \dmd\lib;..\dm\lib and display that list, or
> 2 - let the user specify the lib location in workspace settings, or
> 3 - look for lib files specified in linker options
>
> #3 is probably the best choice.  If a '.lib' is specified in linker options then I will just pass it on the the link process.


\dmd\bin\sc.ini sets the "LIB" Environment like this:
LIB="%@P%\..\lib";\dm\lib
so, both \dmd\lib, \dm\lib are searched when linking.
IMO:
    1) DManager provides a global option to specify lib locations just like
VC6. "Tools|Options|Directories"
then "import files|library files" ....
    this means user can specify his own library path. So every time before
call "DMD" or "Link", the Environment "LIB" should be override. Link process
has a copy of Environment, maybe we can do like this "SET
LIB=%LIB%;D:\MYLIB". But I am not sure.
    Another way: it's user's responsibility to change "SC.ini" manually.
DManager just reads "sc.ini" file and shows those directories in read-only
mode.

    2) Different project has different requirement of libraries. It's
convenient for user to choose libraries for different project. Though VS6
doesn't have this feature --I mean list all libraries in LIB path for user
to choose -- wish DManager to provide this.  in linker options is ok.

again, thanks for your work !

Altair_liu@hotmail.com wrote:

> "David Medlock" <amedlock@nospam.com> wrote:
> 
> 
>>1 - look in \dmd\lib;..\dm\lib and display that list, or
>>2 - let the user specify the lib location in workspace settings, or
>>3 - look for lib files specified in linker options
>>
>>#3 is probably the best choice.  If a '.lib' is specified in linker options then I will just pass it on the the link process.
> 
> 
> 
> \dmd\bin\sc.ini sets the "LIB" Environment like this: LIB="%@P%\..\lib";\dm\lib
> so, both \dmd\lib, \dm\lib are searched when linking.
> IMO:
>     1) DManager provides a global option to specify lib locations just like VC6. "Tools|Options|Directories"
> then "import files|library files" ....
>     this means user can specify his own library path. So every time before call "DMD" or "Link", the Environment "LIB" should be override. Link process has a copy of Environment, maybe we can do like this "SET LIB=%LIB%;D:\MYLIB". But I am not sure.
>     Another way: it's user's responsibility to change "SC.ini" manually. DManager just reads "sc.ini" file and shows those directories in read-only mode.
> 
>     2) Different project has different requirement of libraries. It's convenient for user to choose libraries for different project. Though VS6 doesn't have this feature --I mean list all libraries in LIB path for user to choose -- wish DManager to provide this.  in linker options is ok.
> 
> again, thanks for your work !
> 
> 

You're welcome.

I have made a small change in the short term: When you specify a 'file.lib' entry in the linker options dialog, that file is passed on the command line without any path information during link.

To incorporate a more flexible solution would require that I actually use LINK.exe and not simply rely on dmd.exe .

You can still browse to individual lib files and add them, however.
When you right click a project and select 'Add', you can add any obj or lib files as well as D source files.

In future perhaps I will add .c files as well, and rely on the free digitalmars compiler....