nanogui: Thread: Nano-X and win32

Hi everyone,

I'm trying to build one of the demo from http://www.microwindows.org/ under
Windows...
I understand that everything is made for Linux but I really do need to make
it run on Windows. (C code is portable right?!)

I can compile the demo.  (because of the  prototypes in header files.)
But then, the linker gives me this error: undefined reference to 'GrOpen',
'GrNewWindow", "GrSelectEvents", etc..

How/where can I find these functions?
I added these libraries to the demo project:
- libmwimages.a   (no error)
- libmwin.a           (no error)
- libmwinlib.a        (no error)
- libnano-X.a         (error: "could not read symbols: File in wrong
format")

Does this library contain the functions I am looking for? Does it contain
Linux's symbols?
I also found the client.c which open aconnection to the server, do I needto
implement this "communication" to use Nano-X under Window?

Thank for your time,


Cedric Lescop


PS: I'm new with mailing list, is there any way to do a "browse" in the
SUBJECT or BODY for example? Thank you.

Hi Cedric,

Nano-X gives you two APIs (X-WINDOWS and WIN32 API).
WIN32 API emulates a subset of WIN32 functions.

When you want to program under WINDOWS, you dont need Nano-X libs!

Bye
Uwe

> I'm trying to build one of the demo from
> http://www.microwindows.org/ under
> Windows...
> I understand that everything is made for Linux but I really
> do need to make
> it run on Windows. (C code is portable right?!)
>
> I can compile the demo.  (because of the  prototypes in header files.)
> But then, the linker gives me this error: undefined reference
> to 'GrOpen',
> 'GrNewWindow", "GrSelectEvents", etc..
>
> How/where can I find these functions?
> I added these libraries to the demo project:
> - libmwimages.a   (no error)
> - libmwin.a           (no error)
> - libmwinlib.a        (no error)
> - libnano-X.a         (error: "could not read symbols: File in wrong
> format")
>
> Does this library contain the functions I am looking for?
> Does it contain
> Linux's symbols?
> I also found the client.c which open aconnection to the
> server, do I needto
> implement this "communication" to use Nano-X under Window?
>
> Thank for your time,
>
>
> Cedric Lescop
>
>
> PS: I'm new with mailing list, is there any way to do a
> "browse" in the
> SUBJECT or BODY for example? Thank you.
>

Ok, so if I want to use Nano-X under Windows I need to compile it need
compile it with its win32 API.
Then, if I want to compile it under Windows for a Linux platform, I need to
compile it with NanoX libs (X11).
Is it going to give me the same "result"? That's what people call
"cross-compile"?

Thank you again.

On Mon, Jun 30, 2008 at 11:16 AM, Klatt Uwe ####@####.#### wrote:

> Hi Cedric,
>
> Nano-X gives you two APIs (X-WINDOWS and WIN32 API).
> WIN32 API emulates a subset of WIN32 functions.
>
> When you want to program under WINDOWS, you dont need Nano-X libs!
>
> Bye
> Uwe
>
> > I'm trying to build one of the demo from
> > http://www.microwindows.org/ under
> > Windows...
> > I understand that everything is made for Linux but I really
> > do need to make
> > it run on Windows. (C code is portable right?!)
> >
> > I can compile the demo.  (because of the  prototypes in header files.)
> > But then, the linker gives me this error: undefined reference
> > to 'GrOpen',
> > 'GrNewWindow", "GrSelectEvents", etc..
> >
> > How/where can I find these functions?
> > I added these libraries to the demo project:
> > - libmwimages.a   (no error)
> > - libmwin.a           (no error)
> > - libmwinlib.a        (no error)
> > - libnano-X.a         (error: "could not read symbols: File in wrong
> > format")
> >
> > Does this library contain the functions I am looking for?
> > Does it contain
> > Linux's symbols?
> > I also found the client.c which open aconnection to the
> > server, do I needto
> > implement this "communication" to use Nano-X under Window?
> >
> > Thank for your time,
> >
> >
> > Cedric Lescop
> >
> >
> > PS: I'm new with mailing list, is there any way to do a
> > "browse" in the
> > SUBJECT or BODY for example? Thank you.
> >
>

Hello

Ok, so if I want to use Nano-X under Windows I need to compile it need compile it with its win32 API.
Then, if I want to compile it under Windows for a Linux platform, I need to compile it with NanoX libs (X11).
Is it going to give me the same "result"? That's what people call "cross-compile"?

Hello
 
Can some one guide as how to create a typical GUI with buttons, events handling etc.
 
The API accompanying Tutorial is devoid of these inputs.
 
Where do i get them...???
 
NATARAJAN

--- On Mon, 6/30/08, Klatt Uwe ####@####.#### wrote:

From: Klatt Uwe ####@####.####
Subject: AW: [nanogui] Nano-X and win32
To: "'Cedric Lescop'" ####@####.####
Cc: "'nanoGUI mailing list'" ####@####.####
Date: Monday, June 30, 2008, 6:47 AM

Hello

Ok, so if I want to use Nano-X under Windows I need to compile it need compile
it with its win32 API.
Then, if I want to compile it under Windows for a Linux platform, I need to
compile it with NanoX libs (X11).
Is it going to give me the same "result"? That's what people call
"cross-compile"?


      

For people having the "same" problem as me, just read this first to
understand differences between Microwindows and Nano-X and everything I must
say:
http://microwindows.censoft.com/microwindows_architecture.html
(thank you Klatte & Greg of course)


Natarajan, try this:
-download microwindows full 0.91 here =>
ftp://microwindows.censoft.com/pub/microwindows/
-then look into it for demos: microwindows-0.91\src\demos\nanox\demoxxxx.c


Hope it helps,


Cedric

On Mon, Jun 30, 2008 at 2:18 PM, Natarajan N ####@####.####
wrote:

> Hello
>
> Can some one guide as how to create a typical GUI with buttons, events
> handling etc.
>
> The API accompanying Tutorial is devoid of these inputs.
>
> Where do i get them...???
>
> NATARAJAN
>
> --- On Mon, 6/30/08, Klatt Uwe ####@####.#### wrote:
>
> From: Klatt Uwe ####@####.####
> Subject: AW: [nanogui] Nano-X and win32
> To: "'Cedric Lescop'" ####@####.####
> Cc: "'nanoGUI mailing list'" ####@####.####
> Date: Monday, June 30, 2008, 6:47 AM
>
> Hello
>
> Ok, so if I want to use Nano-X under Windows I need to compile it need
> compile
> it with its win32 API.
> Then, if I want to compile it under Windows for a Linux platform, I need to
> compile it with NanoX libs (X11).
> Is it going to give me the same "result"? That's what people call
> "cross-compile"?
>
>
>
>

: Ok, so if I want to use Nano-X under Windows I need to compile it need
: compile it with its win32 API.
: Then, if I want to compile it under Windows for a Linux platform, I need 
to
: compile it with NanoX libs (X11).
: Is it going to give me the same "result"? That's what people call
: "cross-compile"?

If you're trying to compile up the microwindows distribution
using Windows (say using Cygwin), this has nothing to
do with win32 or nano-X APIs, as these APIs are
implemented by microwindows for ITS applications.

: > > I can compile the demo.  (because of the  prototypes in header files.)
: > > But then, the linker gives me this error: undefined reference
: > > to 'GrOpen',
: > > 'GrNewWindow", "GrSelectEvents", etc..
: > >
: > > How/where can I find these functions?
: > > - libnano-X.a         (error: "could not read symbols: File in wrong
: > > format")

All the GrXXX functions are in libnano-X.a.  Fix your Makefile
or linker commands, the above errors tells you've done
something wrong, since the other libraries are ok.

: > > I also found the client.c which open aconnection to the
: > > server, do I needto
: > > implement this "communication" to use Nano-X under Window?

If you want to RUN nano-X on Windows, then, you have two
choices, you can either link the applications to the server,
LINK_APP_TO_SERVER, or you'll have to implement
a method for interprocess communication, which should work
with some changes to the client.c code.

However, there are a number of other issues, since Windows
doesn't allow direct access to the framebuffer in the same way
as Linux.  I built a Windows screen driver for microwindows
some years ago, along with a number of other changes, if
this is what you're looking for.  I didn't use Cygwin for
this, but built a native port instead. (yes, I know we already
have win32 on win32, but I guess it was for the fun of it,
at the time I was using Windows quite a bit)

If you're cross-compiling for X11 on another platform using
Windows tools, then not much should require change, set the
config file for the target just like on any system.

Regards,

Greg 

> Can some one guide as how to create a typical GUI with buttons, events 
> handling etc.

Microwindows doesn't try to have a complete GUI, instead it
was built more like X11 that allows any number of GUIs to run
on top of it.  GTK, FLTK, and some others are available
for the microwindows nano-X API.  Of course, the win32
API includes buttons, and these are included.

Regards,

Greg 

Thank you for answering, I think I understand better now :)

The 2 things I want to do are:
- To write an application using Nano-X libs running on an embedded ARM
(without running any OS for the moment).
So, if I well understand you: I'll compile up with LINK_APP_TO_SERVER set to
have only one application. Basically, the ARM will run this application
meaning the client will have access to the server (and the GrXXX functions).
I'll need to write the screen driver for the framebuffer blitting. And, I
need to "set up the config file for the target". (I already have a software
to cross-compile application running on the ARM)

- Then, I want to implement the same "behavior" under MS Windows. I know,
sorry, I develop under MS Windows :s
So, if I want to compile up Nano-X with another software, I still set
LINK_APP_TO_SERVER to have one apllication only. And, I'll need to write a
screen driver for accessing the framebuffer under MS Windows. Can I have a
look to the driver you built few years ago for Microwindows?

I still have a question though :p
How can I compile up Microwindows with Nano-X when I'm developping under MS
Windows? For example, "unistd.h" isn't part of MS Windows... I read
somewhere that I can include "io.h" and "process.h" instead...


Regards,


Cedric


On Mon, Jun 30, 2008 at 9:58 PM, Greg Haerr ####@####.#### wrote:

> : Ok, so if I want to use Nano-X under Windows I need to compile it need
> : compile it with its win32 API.
> : Then, if I want to compile it under Windows for a Linux platform, I need
> to
> : compile it with NanoX libs (X11).
> : Is it going to give me the same "result"? That's what people call
> : "cross-compile"?
>
> If you're trying to compile up the microwindows distribution
> using Windows (say using Cygwin), this has nothing to
> do with win32 or nano-X APIs, as these APIs are
> implemented by microwindows for ITS applications.
>
> : > > I can compile the demo.  (because of the  prototypes in header
> files.)
> : > > But then, the linker gives me this error: undefined reference
> : > > to 'GrOpen',
> : > > 'GrNewWindow", "GrSelectEvents", etc..
> : > >
> : > > How/where can I find these functions?
> : > > - libnano-X.a         (error: "could not read symbols: File in wrong
> : > > format")
>
> All the GrXXX functions are in libnano-X.a.  Fix your Makefile
> or linker commands, the above errors tells you've done
> something wrong, since the other libraries are ok.
>
> : > > I also found the client.c which open aconnection to the
> : > > server, do I needto
> : > > implement this "communication" to use Nano-X under Window?
>
> If you want to RUN nano-X on Windows, then, you have two
> choices, you can either link the applications to the server,
> LINK_APP_TO_SERVER, or you'll have to implement
> a method for interprocess communication, which should work
> with some changes to the client.c code.
>
> However, there are a number of other issues, since Windows
> doesn't allow direct access to the framebuffer in the same way
> as Linux.  I built a Windows screen driver for microwindows
> some years ago, along with a number of other changes, if
> this is what you're looking for.  I didn't use Cygwin for
> this, but built a native port instead. (yes, I know we already
> have win32 on win32, but I guess it was for the fun of it,
> at the time I was using Windows quite a bit)
>
> If you're cross-compiling for X11 on another platform using
> Windows tools, then not much should require change, set the
> config file for the target just like on any system.
>
> Regards,
>
> Greg
>
>

Cedric Lescop wrote:
> I still have a question though :p
> How can I compile up Microwindows with Nano-X when I'm developping under MS
> Windows? For example, "unistd.h" isn't part of MS Windows... I read
> somewhere that I can include "io.h" and "process.h" instead...
>
>   

This could depend on your compiler. I hacked together something to do 
limited testing of some of my code and I was able to create an empty 
unistd.h and then just compile. By creating an empty file I don't need 
to edit all the files that include it. If you have missing stuff you 
could find the right include file and add this to your unistd.h.