nanogui: Thread: Nano-X and win32

:  Can I have a
: look to the driver you built few years ago for Microwindows?

Yes, let me see if where it might be...  its a bit old,
but I wrote screen, mouse and keyboard driver and
it all worked, but I think I only got the win32 (singly-linked)
apps to run, since I didn't work on the client/server communications
methods.

:
: 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 depends entirely on your compiler used with its associated
files for the C library.  You'll have to hack code and/or edit
header files.  The best method is to comment out the header
file, look for the errors generated and grep for the proper
header file...  have fun!

Regards,

Greg 

Thank you very much for helping me, I think I understand now :)
Basically, if you want to compile, everything depends on our compiler and
especially its C library. So, it doesn't matter if you're develloping under
MS Windows or Linux if your compiler has the appropriate libraries. I guess
"unistd.h" uses Linux properties, so if I want to compile for MS Windows I
have to write my own "unistd.h" which uses MS Windows properties instead.

Well, I'll do what you said, comment out header files and see if I can
figure out how to solve the errors. I'll start with the srvmain.c. I'll
"remove" its communication part and might make a call to an empty client
function.

Under MS Windows, I think we could use process for the client and server
communicating through unnamed pipes... But since I don't want to use any OS
on my ARM board, I think I could use threads...(if they don't require OS)
 I'll see what I can do.

I'm sure it's going to be fun, thanks again for your time,


Cedric


PS: Greg, hope you didn't lose it, "old" is not "bad" ^^

On Wed, Jul 2, 2008 at 2:55 AM, Greg Haerr ####@####.#### wrote:

> :  Can I have a
> : look to the driver you built few years ago for Microwindows?
>
> Yes, let me see if where it might be...  its a bit old,
> but I wrote screen, mouse and keyboard driver and
> it all worked, but I think I only got the win32 (singly-linked)
> apps to run, since I didn't work on the client/server communications
> methods.
>
> :
> : 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 depends entirely on your compiler used with its associated
> files for the C library.  You'll have to hack code and/or edit
> header files.  The best method is to comment out the header
> file, look for the errors generated and grep for the proper
> header file...  have fun!
>
> Regards,
>
> Greg
>
>

: Well, I'll do what you said, comment out header files and see if I can
: figure out how to solve the errors. I'll start with the srvmain.c. I'll
: "remove" its communication part and might make a call to an empty client
: function.

I would start with setting LINK_APP_INTO_SERVER, this
automatically sets everything so no communications is required.
You don't want to start arbitrarily #ifdefing the source.  The
art of porting is best when you're not mucking around with the
code, but instead configuring for minimal requirements and 
resources until you get something running.  Then you can
start adding back features.  All of the win32 demos
for instance are single-threaded, no client/server.  Its
a great place to start, since the link lines are already
written.

Regards,

Greg

I didn't find any references to LINK_APP_INTO_SERVER in Microwindows 0.91
source code. I used "MS Windows search" which even browses IN files...It
must be somewhere in the Makefile or Config files?!

Anyway, I went through most of the source code files, except the client
side, and I extracted the part I needed I think. I disabled the network
by defining NONETWORK, then I commented out "unisted.h". I only have errors
for the symbols: scrdev, mousedev, kbddev which I was expecting. Those
structures need to be filled in with the drivers functions. I guess now I
need to write drivers to write into the screen through MS Windows, like you
did :)

Regards,

Cedric

On Wed, Jul 2, 2008 at 9:18 PM, Greg Haerr ####@####.#### wrote:

> : Well, I'll do what you said, comment out header files and see if I can
> : figure out how to solve the errors. I'll start with the srvmain.c. I'll
> : "remove" its communication part and might make a call to an empty client
> : function.
>
> I would start with setting LINK_APP_INTO_SERVER, this
> automatically sets everything so no communications is required.
> You don't want to start arbitrarily #ifdefing the source.  The
> art of porting is best when you're not mucking around with the
> code, but instead configuring for minimal requirements and
> resources until you get something running.  Then you can
> start adding back features.  All of the win32 demos
> for instance are single-threaded, no client/server.  Its
> a great place to start, since the link lines are already
> written.
>
> Regards,
>
> Greg
>

:I didn't find any references to LINK_APP_INTO_SERVER in Microwindows 0.91
: source code. I used "MS Windows search" which even browses IN files...It
: must be somewhere in the Makefile or Config files?!

The reference is in src/config.  Then, src/Arch.rules reads the
config file and sets compiler defines.



: Anyway, I went through most of the source code files, except the client
: side, and I extracted the part I needed I think. I disabled the network
: by defining NONETWORK, then I commented out "unisted.h". I only have 
errors
: for the symbols: scrdev, mousedev, kbddev which I was expecting. Those
: structures need to be filled in with the drivers functions.

These structures are initialized in the drivers directory, using
drivers/scr_*.c, drivers/mou_*.c, and drivers/kbd_*.c.


 I guess now I
: need to write drivers to write into the screen through MS Windows, like 
you
: did :)

I sent you my tar file of the Windows version I built, did you get it?

Regards,

Greg