View mode: basic / threaded / horizontal-split · Log in · Help
September 14, 2005
Re: DUI
Ant wrote:
> John Reimer wrote:
> 
>> I'll start testing 
> 
> 
> 
> don't bother.
> I messed up something and now it won't compile on Linux.
> it was working on windows.
> 
> Ant

Strange.  I got it compiling on linux with the build utility just last 
night.  It builds leds too.  Leds will run without a segfault.  Yet I 
can only build everything properly if I use build to build all objects 
at once, that is by letting build collect and compile all required 
source files for DUI and leds.

Where I have complete failure is where I try to use build to create libs 
for libdool.a, libdui.a, and libdantfw.a separately.  It creates the 
libraries just fine... but when I try to build any project like the 
HelloWorld example or Leds, and then link with the build-created 
libraries... the link fails miserably.  I solved this by tacking on 
-L-lphobos (which is already included on the command line from dmd.conf, 
so I shouldn't have to do this);  when I do that, it cleans up all link 
errors and builds the projects and links with the libs.  Unfortunately 
the programs don't run.  They immediately segfault.

So the only way to use build successfully (sadly) with DUI is to avoid 
creating a library.  Let build do what it does best and collect the 
necessary objects from DUI, itself.  I don't like that it doesn't work, 
but I'm at a loss to figure out why. I think this is the same problem I 
was having before, though.  At the very least, I know it's not DUI's 
fault, since it does build and run fine with the other method.

-JJR
September 14, 2005
Re: DUI
John Reimer wrote:
> Ant wrote:
>> John Reimer wrote:
>>
>>> I'll start testing 
>>
>>
>>
>> don't bother.
>> I messed up something and now it won't compile on Linux.
>> it was working on windows.
>>
>> Ant
> 
> [...]  At the very least, I know it's not DUI's
> fault, since it does build and run fine with the other method.
> 

got a workaround:
moved the template aliases to the module where the templates are declared.

tomorrow I'll try to update the sourceforge pages.

Ant
September 14, 2005
Re: DUI
John Reimer wrote:
> Ant wrote:
> 
>> John Reimer wrote:
>>
>>> I'll start testing 
>>
>>
>>
>>
>> don't bother.
>> I messed up something and now it won't compile on Linux.
>> it was working on windows.
>>
>> Ant
> 
> 
> Strange.  I got it compiling on linux with the build utility just last 
> night.  It builds leds too.  Leds will run without a segfault.  Yet I 
> can only build everything properly if I use build to build all objects 
> at once, that is by letting build collect and compile all required 
> source files for DUI and leds.
> 
> Where I have complete failure is where I try to use build to create libs 
> for libdool.a, libdui.a, and libdantfw.a separately.  It creates the 
> libraries just fine... but when I try to build any project like the 
> HelloWorld example or Leds, and then link with the build-created 
> libraries... the link fails miserably.  I solved this by tacking on 
> -L-lphobos (which is already included on the command line from dmd.conf, 
> so I shouldn't have to do this);  when I do that, it cleans up all link 
> errors and builds the projects and links with the libs.  Unfortunately 
> the programs don't run.  They immediately segfault.
> 
> So the only way to use build successfully (sadly) with DUI is to avoid 
> creating a library.  Let build do what it does best and collect the 
> necessary objects from DUI, itself.  I don't like that it doesn't work, 
> but I'm at a loss to figure out why. I think this is the same problem I 
> was having before, though.  At the very least, I know it's not DUI's 
> fault, since it does build and run fine with the other method.
> 
> -JJR

I tried to use the sourceforge version a few months ago. There was some 
linking issues, but eventually I got it working. BTW, how is it possible 
that DUI links properly only when the compiler include-paths are set in 
a specific order.
September 14, 2005
Re: DUI
In article <dg82f4$2o6n$1@digitaldaemon.com>, Ant says...

>with he same license as phobos (GPL + Artistic - as I remember)

You're confusing things here. It's the DMD front end that is released under GPL
and Artistic license. Phobos is released under a permissive MIT/ZLIB type
license. (I don't know which one exactly, and if it's always the same, but it
doesn't matter since I believe they say almost the same.)

Def
September 14, 2005
Re: DUI
Jari-Matti Mäkelä wrote:

> 
> 
> I tried to use the sourceforge version a few months ago. There was some 
> linking issues, but eventually I got it working. BTW, how is it possible 
> that DUI links properly only when the compiler include-paths are set in 
> a specific order.

Were you using the dyndui version of dui?  Were you using build?  If it 
was a few months ago, you may have been using a version that did work. 
Now I can't seem to get it to work as I described.

What do you mean about the include-path order?  Is that what you were 
doing to get it working?  That would be strange;  I can't see how 
include-path order on the command line would have any effect on success 
or failure. Library order, on the other hand...

-JJR
September 14, 2005
DUI license (was: DUI)
In article <dg82f4$2o6n$1@digitaldaemon.com>, Ant says...

>I want to go with something less restrictive.
>but it's very confusing.
>I want to include the documentation from GTK into the code comments
>and I don't know if I can do it.
>I guess it will be simple to strip the comments out if necessary.

BTW, have you confirmed that the license of the GTK documentation that you
want to use in your comments is actually under the LGPL? Or is there
another license for the docs? Or is it simple copyright, similar to what
Walter uses for his D documentation?

Def
September 14, 2005
Re: DUI
John Reimer wrote:
> Jari-Matti Mäkelä wrote:
> 
>>
>>
>> I tried to use the sourceforge version a few months ago. There was 
>> some linking issues, but eventually I got it working. BTW, how is it 
>> possible that DUI links properly only when the compiler include-paths 
>> are set in a specific order.
> 
> 
> Were you using the dyndui version of dui?  Were you using build?  If it 
> was a few months ago, you may have been using a version that did work. 
> Now I can't seem to get it to work as I described.
> 
> What do you mean about the include-path order?  Is that what you were 
> doing to get it working?  That would be strange;  I can't see how 
> include-path order on the command line would have any effect on success 
> or failure. Library order, on the other hand...
> 
> -JJR

I tried the old sourceforge version on Linux. I didn't use Build so I 
needed to modify the include path order manually in the makefile. I 
haven't used DUI for a while, but if a new "stable" version is coming, 
it might be worth testing. Does it already support GTK+ 2.8?
September 14, 2005
Re: DUI license (was: DUI)
In article <dg9stv$1s0l$1@digitaldaemon.com>, Def says...
>
>In article <dg82f4$2o6n$1@digitaldaemon.com>, Ant says...
>
>>I want to go with something less restrictive.
>>but it's very confusing.
>>I want to include the documentation from GTK into the code comments
>>and I don't know if I can do it.
>>I guess it will be simple to strip the comments out if necessary.
>
>BTW, have you confirmed that the license of the GTK documentation that you
>want to use in your comments is actually under the LGPL? Or is there
>another license for the docs? Or is it simple copyright, similar to what
>Walter uses for his D documentation?
>
>Def

I'll have to review that.
I asked on the GTK group once.
what I remember is that I couldn't do it
but also the all thing wasn't too clear.

Ant
September 14, 2005
Re: DUI
In article <dg9tun$1tj6$1@digitaldaemon.com>,
=?ISO-8859-1?Q?Jari-Matti_M=E4kel=E4?= says...
>
>
>I tried the old sourceforge version on Linux. I didn't use Build so I 
>needed to modify the include path order manually in the makefile. I 
>haven't used DUI for a while, but if a new "stable" version is coming, 
>it might be worth testing. Does it already support GTK+ 2.8?

stable :)

I do run leds for days (on linux) with no problems,
but DUI is still a work in progress.

There are improvements but DUI is basically at 2.4 + comboBox and fileChooser
from 2.6.
GTK+ 2.8 works fine but 2.8 features don't have a binding/wrap on DUI.

DUI on linux is still better than on window.
Meanwhile GTK+ for windows is much better than a year ago,
one can notice it immidiatly on the DUITests.

I'll try to update the sourceforce pages
(well, I'm taking work home today... :( )

Ant
September 17, 2005
Re: DUI
John Reimer wrote:
> Ant wrote:
>> John Reimer wrote:
>>
>>> I'll start testing 
>>
>>
>>
>> don't bother.
>> I messed up something and now it won't compile on Linux.
>> it was working on windows.
>>
>> Ant
> 
> Strange.  I got it compiling on linux with the build utility just last 
> night.  It builds leds too.  Leds will run without a segfault.

Is this linux?

can you turn on the outline, open a source file,
go to the outline browser and back to the project browser?
that will segfault leds for me on linux.

(color bug workaround - after turning on the outline the window
background will became black:
go to Edit/preferences/D/Editor/Color to reset the background)


Ant
1 2 3
Top | Discussion index | About this forum | D home