Re: [Simulavr-devel] SimulAvrxx for Win32/don't build for TCL if no TCL

[Bill]

Thanks to Kai, and Thanks to Oleg's prodding, I have commited several
build-related changes to CVS.

1.)
It turns out that with the latest "cygwin" environment, simulavrxx
bulids successfully on the Microsoft Windows platform. (I personally
built it on MS/Win2k) Make sure that if you built binutils with
"--prefix=/x/y/z" that /x/y/z/bin is in your path or you will need to
tell ./configure where the tools are. (by default, /usr/local will be
used, which should be fine)

I have not tested it on Ms/Win32 yet, so beware though. YMMV ;-)

Now a questions: Who can make a cygwin package for this that can be
added to the "cygwin"'s setup program? I have looked into this a bit, it
looks like it should be pretty straightforward technically, but it would
need a cygwin maintainer I think, if I remember the cywin rules.

2.)
Oleg was kind enough to submit a great patch to change how the build
works. I am a bit stubborn, so I looked it over and didn't exaclty
accept his patch, but I think I did solve the problems he was pointing
out, at least to a large degree.

I'm sure I'll hear about it if I missed anything ;-) (seriously, if I
haven't made life easier or there are more things you would like to see
different, please let me know. No promises, but I really appreciated
Oleg's approach to this)



Kai Klenovsek wrote:

>Ok, here is a small list what i did. I`m sure it isn`t complete because 
>i have a lot of additional tools and libs installed.
>
>1. Following folders i added to my path enviroment variable:
>cygwin/bin
>cygwin/usr/local/bin 
>
>2. Binutils-2.16
> ./configure --target=avr --enable-install-libbfd --disable-nls
>
>3. Changing "_coocked_size" --> "size" in avrdevice.cpp (Hint from Klaus for
>Binutils-2.16).
>
>4. Put an epmpty file with name "simulavr_wrap.cpp" into SimulAvrxx source
>folder. 
>
>5. SimulAvrxx-0.8.005
> ./configure --with-bfd-patch=c:/cygwin/home/user/binutil-2.16/bfd
>
>
>If it is working for you, i would be glad if the output filename could be
>changed official 
>to simulavrxx.exe to avoid name overlaps with the real Simulavr.exe in the
>output folder.
> 
>Ciao,
>Kai
>
>
> 
>  
>
>>Ahhh.... I see!
>>
>>Ok. Last I knew this didn't work.
>>
>>Could you tell me exactly how you built this? i.e. how you
>>configured/installed binutils, what version of binutils, what flags did
>>you give simulavr etc.?
>>
>>I tried to reproduce what you did, but it didn't work due to
>>inconsistencies between libbfd and libiberty it seemed....it got further
>>than I expected, so it sounds like we are close to having win32 support.
>>;-)
>>
>>Cheers,
>>
>>Bill
>>
>>Kai Klenovsek wrote:
>>
>>    
>>
>>>Hi,
>>>
>>>i built this version without any code changes in cygwin dll or
>>>      
>>>
>>simulavrxx.
>>    
>>
>>>It was a little bit crappy but it seems to work.
>>>
>>>Ciao,
>>>Kai
>>>
>>> 
>>>
>>>      
>>>
>>>>Thanks, but this doesn't help us. All I saw was the exe and dll. I
>>>>need source code.
>>>>
>>>>Would you mind emailing me a zip or tbz2 or something of your source
>>>>code tree so I can build in on my win2k box under cygwin?
>>>>
>>>>One word of caution about cygwin1.dll. There are rules you must follow
>>>>if you distribute cygwin1.dll. Please see the cygwin project archives
>>>>for the conditions. (it doesn't look like you followed those rules)
>>>>This doesn't matter to simulavr development becuase we distribute
>>>>sources...how you as a customer build it is up to you of course.
>>>>
>>>>Anyway, I would gladly incorporate your changes to add cygwin as a
>>>>supported platform.
>>>>
>>>>Cheers,
>>>>Bill
>>>>
>>>>
>>>>Kai Klenovsek wrote:
>>>>
>>>>   
>>>>        
>>>>