nanogui: Compile with DJGPP or MSC


Previous by date: 22 May 2011 14:06:47 -0000 amd64, freetype and t1lib, sibu xolo
Next by date: 22 May 2011 14:06:47 -0000 Re: amd64, freetype and t1lib, Greg Haerr
Previous in thread: 22 May 2011 14:06:47 -0000 Re: Compile with DJGPP or MSC, Georg Potthast
Next in thread: 22 May 2011 14:06:47 -0000 Re: Compile with DJGPP or MSC, Greg Haerr

Subject: Re: [nanogui] Compile with DJGPP or MSC
From: "Georg Potthast" ####@####.####
Date: 22 May 2011 14:06:47 -0000
Message-Id: <001301cc1889$7aede920$a900a8c0@SCHREIBTISCHGP>

I managed to get version 0.91 to compile with DJGPP and most of the samples run OK.

However, when compiling 0.92 only a few samples still work. The 0.92 snapshot does compile but the samples do not work at all any more.

Since the documentation describes Nano-X as a modular architecture, is it possible to use the old drivers with the 0.92 versions? They have moved to the depreciated directory. Why did you drop the code that supported these drivers and could it not be made optional instead? Can I just replace the new fblinxx drivers with the old ones or has the code also changed that used these?

I have seen there is a member in the MWSCREENINFO structure: 
MWBOOL fbdriver; /* true if running mwin fb screen driver*/

What does Nano-X do if you set this to FALSE? 

Georg



Previous by date: 22 May 2011 14:06:47 -0000 amd64, freetype and t1lib, sibu xolo
Next by date: 22 May 2011 14:06:47 -0000 Re: amd64, freetype and t1lib, Greg Haerr
Previous in thread: 22 May 2011 14:06:47 -0000 Re: Compile with DJGPP or MSC, Georg Potthast
Next in thread: 22 May 2011 14:06:47 -0000 Re: Compile with DJGPP or MSC, Greg Haerr


Powered by ezmlm-browse 0.20.