RE: [ECOS] Building the Host tools on Windows

[Srdjan Sobajic <srdjans at digitalpersona dot com>]

So I grabbed the latest stuff from CVS this morning and everything works
like a charm!
Thanks!

BTW. I think that there are two really minor issues still:

1) The splsh16.bmp image in the host\tools\configtool\standalone\win32\res
directory
is messed up. Please check it out and take a look. (there is a shift of the
middle section
of the image to the right.)

2) When building the Configtool project (the one thats build using VC),
there are some warnings
about the help files not being there... I guess it's to be expected.

I've added some responses to your comment below:

> > 1. When getting the eCos sources from CVS using WinCVS, it 
> appears necessary
> > 
> > to set the CRLF translation (in the Global Settings dialog) 
> to UNIX mode for
> > 
> > getting the eCos package subdirectory, and to DOS mode for 
> getting the host
> > subdirectory. If you check out the host tools under UNIX 
> mode, VC can't open
> > 
> > the .dsw. Effectively, you can't get the whole thing in one pass...
> 
> Things may be different with the command-line cvs client - or 
> did you make
> WinCVS use that?

I just used WinCVS in the default mode (so no command line client). I will
have to try
that sometime, but for now, I think this should be made a little clearer.

> > Also, make sure you have installed VC6 with all the MFC 
> options. On my
> > machine, I needed mfc42u.lib, which is the Unicode version 
> of MFC, and which
> > 
> > may not be installed by default everywhere.
> 
> We always ship the ANSI build - for Win95/98/ME 
> compatibility. We always
> develop with the Unicode version to catch Unicode/ANSI conversion bugs
> early. If you switch to the ANSI release configuration, you 
> need mfc42.lib,
> not mfc42u.lib, etc.

OK. It works just fine as you said if I choose the ANSI release build.

> > 7. In VC6, once the project has been loaded, look at the 
> files in the "cdl"
> > project. Specifically, open the settings (by right clicking) for the
> > ChangeLog
> > file. In the "Custom Build" tab, edit the command line (at 
> the end) to point
> > 
> > to the proper TCL installation directories. Specifically, 
> it is necessary to
> > 
> > set
> > --with-tcl_version=83 --with-tcl-lib=/c/tcl/lib
> > --with-tcl-header=/c/tcl/include
> > 
> > ** NOTE Even after doing this, during the configure steps I 
> see configure
> > picking up tcl from /usr/lib.
> 
> This aspect should be fixed in the anon cvs update. The 
> custom build step
> shold be able to refer to the TCLHOME variable.


Yep, It works wonderfully now. Picks up everything from TCLHOME correctly. 
I just need to set the TCL version information correctly throughout the
projects.

BTW, do you think it'd be worth having a TCLVERSION env variable to set the
version
throughout the projects, so that the VC linker will get the right version of
the tcl8x.lib
and so that you don't have to mess around the custom build step parameters?
Especially, since you
have to change it on every project and for all configurations... (I know,
no-one is going build
the other configurations, but still....)

If you're still interested I can send you a diff vs the README file. Should
I?

Srdjan