delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2011/05/15/16:20:43

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: DJGPP AT delorie DOT com
Date: Sun, 15 May 2011 15:20:20 -0500
From: "John Wright" <john AT wacontrols DOT com>
To: DJGPP AT delorie DOT com
Cc: halo1 AT inter DOT net DOT il
Subject: Fw: DJGPP V1.12 & Desqview/X QDLIb200 Compile - SUCCESSFUL
Message-ID: <c2a9e336d4d530cfd20ed021e5c182b0@wacontrols.com>
X-Mailer: IceWarp Web Mail 5.6.7
X-Originating-IP: 205.209.233.212
MIME-Version: 1.0
Reply-To: "John Wright" <john AT wacontrols DOT com>

This is a multi-part message in MIME format.
----4D8837D1F697082645640A09AF878B66
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

I did not see everyone's reply until I read the daily digest. It appears that 128MB memory is not an issue on this machine with V1. Everything is okay using QDLIB200. My ~\lib path was wrong for QDLib200, and QDDVX102 sources were not working either so that threw me off.  I guess QDDVX102 and anything before that could be considered functionally obsolete. It appears that both toolkits are incomplete in some ways. I was looking for the periodic table of widgets in ~\Examples, but it's not there. So far, I'm very happy with the way everything is work working. DVX seem to be very stable. I have not had any problems compiling or running Emacs in a scaled Dos window.

I've got some other questions that I will start new threads for.

-----Original message-----

From: "John Wright" john AT wacontrols DOT com
Date: Sat, 14 May 2011 10:09:58 -0500
To: djgpp AT delorie DOT com
Subject: DJGPP V1.12  & Desqview/X QDLIb200 Compile - SUCCESSFUL

Well my bad. I had a bad library path which was hard to see because there are too many DJGPP path references. Whoever put QDLIB200 together put X11 library files in the directory of C:\dvx\lib\djgpp. My library path was set to C:\dvx\lib; I just could not see it.

I guess I have some configuration problem with QDDVX102 library.  The X11 libraries are older and makefile definitions are a little different than what is in QDLIB200 and QDtkt200. 

Oh Well, now I can move on...
----4D8837D1F697082645640A09AF878B66
Content-Type: message/rfc822; name="DJGPP V1.12  & Desqview/X QDLIb200 Compile - SUCCESSFUL"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="DJGPP V1.12  & Desqview/X QDLIb200 Compile - SUCCESSFUL"

Date: Sat, 14 May 2011 10:09:58 -0500
From: "John Wright" <john AT wacontrols DOT com>
Reply-To: "John Wright" <john AT wacontrols DOT com>
To: djgpp AT delorie DOT com
Subject: DJGPP V1.12  & Desqview/X QDLIb200 Compile - SUCCESSFUL
Message-ID: <9c2af38991bd092b6ba449b9ff5c835b AT wacontrols DOT com>
X-Mailer: IceWarp Web Mail 5.6.7
X-Originating-IP: 205.209.233.212
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Well my bad. I had a bad library path which was hard to see because there are too many DJGPP path references. Whoever put QDLIB200 together put X11 library files in the directory of C:\dvx\lib\djgpp. My library path was set to C:\dvx\lib; I just could not see it.

I guess I have some configuration problem with QDDVX102 library.  The X11 libraries are older and makefile definitions are a little different than what is in QDLIB200 and QDtkt200. 

Oh Well, now I can move on...
----4D8837D1F697082645640A09AF878B66--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019