www.digitalmars.com         C & C++   DMDScript  

c++.wxwindows - wxwindows 2.4.2

reply chris elliott <biol75 york.ac.uk> writes:
Hi

Wxwindows 2.4.2 stable release is now on-line at 
http://biolpc22.york.ac.uk/pub/2.4.2/

(see also http://www.wxwindows.org/)

This has full support for compiling with d-mars compiler version 8.34 
and later

known bug: reading jpegs doesn't work (code compiles, but does not link)

Feel free to report more bugs here, or on the wx-dev mailing list

have fun!
chris
Sep 23 2003
next sibling parent "Charles Sanders" <sanders-consulting comcast.net> writes:
Coolness thanks for the link!

C
"chris elliott" <biol75 york.ac.uk> wrote in message
news:bkosn2$29u9$1 digitaldaemon.com...

 Hi

 Wxwindows 2.4.2 stable release is now on-line at
 http://biolpc22.york.ac.uk/pub/2.4.2/

 (see also http://www.wxwindows.org/)

 This has full support for compiling with d-mars compiler version 8.34
 and later

 known bug: reading jpegs doesn't work (code compiles, but does not link)

 Feel free to report more bugs here, or on the wx-dev mailing list

 have fun!
 chris
Sep 23 2003
prev sibling parent reply "Walter" <walter digitalmars.com> writes:
"chris elliott" <biol75 york.ac.uk> wrote in message
news:bkosn2$29u9$1 digitaldaemon.com...

 Hi

 Wxwindows 2.4.2 stable release is now on-line at
 http://biolpc22.york.ac.uk/pub/2.4.2/


I'm missing something. I downloaded it, but it contains no information on
how to compile with Digital Mars C++. Can you point me to the right file
with instructions in it? Thanks.
Sep 30 2003
parent reply Arjan Knepper <arjan ask.me> writes:
I think if you use the patchkit from the 
http://www.digitalmars.com/~arjan and just follow the instructions you 
will be fine with 2.4.2 too.

Arjan

Walter wrote:


 "chris elliott" <biol75 york.ac.uk> wrote in message
 news:bkosn2$29u9$1 digitaldaemon.com...
 

Hi

Wxwindows 2.4.2 stable release is now on-line at
http://biolpc22.york.ac.uk/pub/2.4.2/


 
 
 I'm missing something. I downloaded it, but it contains no information on
 how to compile with Digital Mars C++. Can you point me to the right file
 with instructions in it? Thanks.
Sep 30 2003
parent reply Werner Smekal <Werner_member pathlink.com> writes:
Hi,

you don't need any patch, just go to $(WXDIR)/src/msw, where WXDIR is set to the
wxwindows path (there should be no spaces there). First you may set some stuff
in $(WXDIR)/include/wx/msw/setup.h (see there).
Then run the makefile: make -f makefile.sc and a debug library will be built in
$(WXDIR)/lib
possible options:
make -f makefile.sc FINAL=1 (release lib)
make -f makefile.sc DLL=1 (dll)
make -f makefile.sc DLL=1 FINAL=1 (dll, release)
make -f makefile.sc HYBRID=1 (debug version, but without debug information, so
wxASSERT is still working and so on)

Maybe I missed something or wrote wrong, but this is all as far as I remember
for the command line version. Practically read in $(WXDIR)/doc/msw/install.txt
the borland bcc55++ part and change makefile.b32 to makefile.sc also for
compiling the samples then.

regards,
Werner

PS: Thanks to everybody who helped making wxwindows work with dmc.


In article <blcj6v$19dr$1 digitaldaemon.com>, Arjan Knepper says...

I think if you use the patchkit from the 
http://www.digitalmars.com/~arjan and just follow the instructions you 
will be fine with 2.4.2 too.

Arjan

Walter wrote:


 "chris elliott" <biol75 york.ac.uk> wrote in message
 news:bkosn2$29u9$1 digitaldaemon.com...
 

Hi

Wxwindows 2.4.2 stable release is now on-line at
http://biolpc22.york.ac.uk/pub/2.4.2/


 
 
 I'm missing something. I downloaded it, but it contains no information on
 how to compile with Digital Mars C++. Can you point me to the right file
 with instructions in it? Thanks.
Oct 01 2003
parent reply "_" <mjoyl lineone.netX> writes:
"Werner Smekal" <Werner_member pathlink.com> wrote in message
news:blgad5$lod$1 digitaldaemon.com...

 Hi,

 you don't need any patch, just go to $(WXDIR)/src/msw, where WXDIR is set


to the

 wxwindows path (there should be no spaces there). First you may set some


stuff

 in $(WXDIR)/include/wx/msw/setup.h (see there).
 Then run the makefile: make -f makefile.sc and a debug library will be


built in

 $(WXDIR)/lib
 possible options:
 make -f makefile.sc FINAL=1 (release lib)
 make -f makefile.sc DLL=1 (dll)
 make -f makefile.sc DLL=1 FINAL=1 (dll, release)
 make -f makefile.sc HYBRID=1 (debug version, but without debug


information, so

 wxASSERT is still working and so on)

 Maybe I missed something or wrote wrong, but this is all as far as I


remember

 for the command line version. Practically read in


$(WXDIR)/doc/msw/install.txt

 the borland bcc55++ part and change makefile.b32 to makefile.sc also for
 compiling the samples then.

 regards,
 Werner


Maybe I'm missing something here but I've been trying wxwindows 2.4.1 with
the dmc patch and 2.4.2 without the patch (obviously) both with 8.38 of dmc
and I can't get much to run out of the wrapper so to speak... when trying to
build the base libraries the make -f makefile.sc terminates on the first
compile line after implib creates some def files... the final command that
fails is:

dmc -cpp -Ae -Ar -mn -D_WINDOWS -6 -a8 -Nc -c -H -HD..\..\d_mars -HO- -DWXMS
W -D
__WIN32__ -D__WIN95__ -D__WXDEBUG__  -I..\..\include -I..\..\lib\_sc -I..\..
\con
trib\include -I..\../src/regex;..\../src/png;..\../src/jpeg;..\../src/zlib;.
.\..
/src/tiff -HF..\..\d_mars\wxprec.SYM -o..\..\d_mars\wxprec.PCO
..\..\include\wx\
wxprec.h
Error: command line too long

According to my understanding lines like that are way in excess of
command.com ability to send to a program... I get the same with building
libs the patched 2.4.1 version with lib creation failing because of over a
hundred .obj file specs dumped into a single command line. What gives? I am
using:


Digital Mars Make Version 5.00
Copyright (C) Digital Mars 1985-2000.  All Rights Reserved.
Written by Walter Bright

If I manually redirect the make error output to a text file then copy the
command line upto the end of the lib definition and leave the looooooong
list of obj files on the single line, and remove the error message, then
save the file I can then build the lib by doing something like:
lib -c -p256 %wxwin%\lib\dmc\dmc_jpeg.lib  obj.lst

it is possible to go through the entire process until all component libs are
created but that does not solve the problem that the same happens with
wxHatch where the final link command line is massive too and produces the
same error.

Is this a problem with my system alone or a feature of the non-cd version of
the make.exe to not provide an automated way to generate   list files for
excessively long commandlines?

Thanks in advance for any help. and apologies if it has been answered
elsewhere, I have looked some but not found anything and as yet I'm just
trying to learn a bit of C/C++ and maybe create some tools I've needed for a
while, I didn't expect to have to learn make.exe tricks and re-write make
files just to compile some examples or use wxHatch :-(
Dec 14 2003
parent "_" <mjoyl lineone.netX> writes:
"_" <mjoyl lineone.netX> wrote in message
news:brisfu$jkk$1 digitaldaemon.com...

 "Werner Smekal" <Werner_member pathlink.com> wrote in message
 news:blgad5$lod$1 digitaldaemon.com...

 Hi,

 you don't need any patch, just go to $(WXDIR)/src/msw, where WXDIR is




set

 to the

 wxwindows path (there should be no spaces there). First you may set some


 stuff

 in $(WXDIR)/include/wx/msw/setup.h (see there).
 Then run the makefile: make -f makefile.sc and a debug library will be


 built in

 $(WXDIR)/lib
 possible options:
 make -f makefile.sc FINAL=1 (release lib)
 make -f makefile.sc DLL=1 (dll)
 make -f makefile.sc DLL=1 FINAL=1 (dll, release)
 make -f makefile.sc HYBRID=1 (debug version, but without debug


 information, so

 wxASSERT is still working and so on)

 Maybe I missed something or wrote wrong, but this is all as far as I


 remember

 for the command line version. Practically read in


 $(WXDIR)/doc/msw/install.txt

 the borland bcc55++ part and change makefile.b32 to makefile.sc also for
 compiling the samples then.

 regards,
 Werner


 Maybe I'm missing something here but I've been trying wxwindows 2.4.1 with
 the dmc patch and 2.4.2 without the patch (obviously) both with 8.38 of


dmc

 and I can't get much to run out of the wrapper so to speak... when trying


to

 build the base libraries the make -f makefile.sc terminates on the first
 compile line after implib creates some def files... the final command that
 fails is:


dmc -cpp -Ae -Ar -mn -D_WINDOWS -6 -a8 -Nc -c -H -HD..\..\d_mars -HO- -DWXMS

 W -D


__WIN32__ -D__WIN95__ -D__WXDEBUG__  -I..\..\include -I..\..\lib\_sc -I..\..

 \con


trib\include -I..\../src/regex;..\../src/png;..\../src/jpeg;..\../src/zlib;.

 .\..
 /src/tiff -HF..\..\d_mars\wxprec.SYM -o..\..\d_mars\wxprec.PCO
 ..\..\include\wx\
 wxprec.h
 Error: command line too long

 According to my understanding lines like that are way in excess of
 command.com ability to send to a program... I get the same with building
 libs the patched 2.4.1 version with lib creation failing because of over a
 hundred .obj file specs dumped into a single command line. What gives? I


am

 using:


 Digital Mars Make Version 5.00
 Copyright (C) Digital Mars 1985-2000.  All Rights Reserved.
 Written by Walter Bright


This is the source of the problem version 5.00 is the one linked for
download on the digitalmars front page... I downloaded it thinking it was
some kind of improvememnt over the stock make.exe that was part of the
package and saved it over the top of the original without checking versions
or anything, turns out that one is an old obsolete one and current package
uses 5.04 that impliments a new rule flag ~ that forces use of  
enviroinment response file that lets massive parameter lists be passed
without batting an eyelid. Victor, any reason why that old make.exe is on
your page for download if it's inferior to the current release version?
Dec 14 2003