nanogui: Thread: make errors in 0.89pre2

Hi 

Just download the latest source 0.89pre2 nad tried to
build microwindows on linux. I got few errors while
building. Still could not build nano-X. I beg your
pardon for not looking very deeply into thoes errors.
I am still looking into it. Just thought to anyhow
post it, if these are known errors. The error log and
config files are attached. Please tell where am I
going wrong. 

Thank you,
Maneesh

  

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

Hi,

With some more trial and error I could build nano-X.
This time I just copied the config.x11 to config and
did make clean; make, and it worled. But I could not
understand why if I configure with xconfigure I am not
getting it built. Anyway sorry for bothering...

Thank you 
Maneesh

 


__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

If the option SHAREDLIBS is turned on and T1LIB support
or FREETYPE support is also turned on,
the compilation of nano-X will fail.

Need to modify Makefile.rules:

From:
ifeq ($(HAVE_T1LIB_SUPPORT), Y)
MWINLIBS += $(LIBT1LIB)
CCMWINLIBS += $(LIBT1LIB)
NANOXLIBS += $(LIBT1LIB)
NANOXSERVERLIBS += $(LIBT1LIB)
ifeq ($(LINK_APP_INTO_SERVER), Y)
NANOXCLIENTLIBS += $(LIBT1LIB)
endif
endif

To:
ifeq ($(HAVE_T1LIB_SUPPORT), Y)
MWINLIBS += $(LIBT1LIB)
CCMWINLIBS += $(LIBT1LIB)
NANOXLIBS += $(LIBT1LIB)
NANOXSERVERLIBS += $(LIBT1LIB)
ifeq ($(SHAREDLIBS), Y)
        CCNANOXSERVERLIBS += $(LIBT1LIB)
endif
ifeq ($(LINK_APP_INTO_SERVER), Y)
NANOXCLIENTLIBS += $(LIBT1LIB)
endif
endif

From:
ifeq ($(HAVE_FREETYPE_SUPPORT), Y)
MWINLIBS += $(LIBFTLIB)
CCMWINLIBS += $(LIBFTLIB)
NANOXLIBS += $(LIBFTLIB)
NANOXSERVERLIBS += $(LIBFTLIB)
ifeq ($(LINK_APP_INTO_SERVER), Y)
NANOXCLIENTLIBS += $(LIBFTLIB)
endif
endif

To:
ifeq ($(HAVE_FREETYPE_SUPPORT), Y)
MWINLIBS += $(LIBFTLIB)
CCMWINLIBS += $(LIBFTLIB)
NANOXLIBS += $(LIBFTLIB)
NANOXSERVERLIBS += $(LIBFTLIB)
ifeq ($(LINK_APP_INTO_SERVER), Y)
NANOXCLIENTLIBS += $(LIBFTLIB)
endif
endif


Murphy C. Chen                          ####@####.####
HsinChu, Taiwan, ROC.                   http://murphy.somewhere.net/

: Just download the latest source 0.89pre2 nad tried to
: build microwindows on linux. I got few errors while
: building. 

Yes, these errors occur when building with
LINK_APP_INTO_SERVER=Y.  I didn't
spend too much time with this option.  There
were several changes with the new window
manager that don't have link-in APIs.
I'm working on a version that won't require
a separate process for the window manager,
for systems that aren't multi-processed.

Set LINK_APP_INTO_SERVER=N
and you'll be able to build Nano-X.

Regards,

Greg

: But I could not
: understand why if I configure with xconfigure I am not
: getting it built. 

Several new config options have been added, and
the xconfigure script, written in wish, hasn't been
updated.

Regards,

Greg

Forgive me, but have you ever considered a simpler make system with standard
include files for options?  I think most programmers are much more
comfortable working with a 1200 line include file than a 1200 line long
makefile.

As a side note, I'm finally getting enough time to start work on a VxWorks
port.  I'll be trying to get it running on a MIPSR3000(big endian mode) with
an IGST Cyberpro 5050 on the PCI bus.  In the process, I'd really like to
restructure the make system and the directory tree.  If its O.K. with
everyone, I'd like to make this alternate configuration available for
feedback.

Another side note:  The GPL'd code still exists in the tree I got from CVS
last night.  I don't know how much everyone cares, but that is a problem
because the GPL (from what I read at
http://gnu.sote.hu/philosophy/license-list.html#GPLIncompatibleLicenses) is
not compatible with the MPL.  So we're not allowed to link the two together.
Also it presents a problem for commercial developers(like myself) who
respect the wishes of the FSF(even though we may think they're highly
annoying! :) ).

Thanks!
Jason
{
   Jason Gaiser                    		phone:  (858) 824-3078
   Wind River Doctor Design Services	fax: (858) 824-3178
   ####@####.####			http://www.doctordesign.com
}




> -----Original Message-----
> From: Greg Haerr ####@####.####
> Sent: Wednesday, October 04, 2000 9:16 AM
> To: Maneesh Soni; 
> Subject: Re: make errors in 0.89pre2
> 
> 
> : But I could not
> : understand why if I configure with xconfigure I am not
> : getting it built. 
> 
> Several new config options have been added, and
> the xconfigure script, written in wish, hasn't been
> updated.
> 
> Regards,
> 
> Greg
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 

: Forgive me, but have you ever considered a simpler make system with
standard
: include files for options?  I think most programmers are much more
: comfortable working with a 1200 line include file than a 1200 line long
: makefile.

Which 1200 line makefiles are you talking about?  I'm interested
in a simpler make system, but I'm not really tracking what you're
suggesting.  If you're talking about xconfigure, that's not really
part of the make system, but a config file generator.



:
: As a side note, I'm finally getting enough time to start work on a VxWorks
: port.  I'll be trying to get it running on a MIPSR3000(big endian mode)
with
: an IGST Cyberpro 5050 on the PCI bus.

Cool.


 In the process, I'd really like to
: restructure the make system and the directory tree.  If its O.K. with
: everyone, I'd like to make this alternate configuration available for
: feedback.

I'm always up for a simpler make system, I'd like to hear your
suggestions before you go to the trouble of rewriting it, to
better ensure it's inclusion.  What are you thinking of in terms of the
directory tree?



:
: Another side note:  The GPL'd code still exists in the tree I got from CVS
: last night.  I don't know how much everyone cares, but that is a problem
: because the GPL (from what I read at
: http://gnu.sote.hu/philosophy/license-list.html#GPLIncompatibleLicenses)
is
: not compatible with the MPL.  So we're not allowed to link the two
together.
: Also it presents a problem for commercial developers(like myself) who
: respect the wishes of the FSF(even though we may think they're highly
: annoying! :) ).

Which files are you talking about?  I'm only aware of one file which
I used about two routines, in the arc/pie stuff.   There should be no
other GPL files in the distribution, other than complete applications
like nxscribble that don't get linked with the server.

Regards,

Greg