SE 1.2r6 on Windows build question

[Grant Rettke]

Hi,

I just successfully build SE 1.2r6 on Windows XP Pro by performing the
following
steps (and I've got a question).

Downloaded install.exe and SmartEiffel-1.2r6.tar.

Extracted the tar to c:\ and copied the install.exe into
that directory.

Added to ENV:

SMARTEIFFELDIR=C:\SmartEiffel12
SMARTEIFFELDIRECTORY=c:\SmartEiffel12
SMARTEIFFEL=%SMARTEIFFELDIR%\sys\system.se

Added the se bin dir for the path.

Went to dos
Ran vcvars32.bat for the VC++ 2003 Toolkit
set INCLUDE=%INCLUDE%;C:\Program Files\Microsoft Visual Studio
8\VC\PlatformSDK\Include
set LIB=%LIB%;C:\Program Files\Microsoft Visual Studio 8\VC\lib
ran install.exe and chose defaults and then 'cl'.

Here is the question. I used VC++ 2003 to compile the app, but I ended
up using libraries and headers from VC++ 2005. Everything seemed to
work fine. I ran the pretty printer and that seemed to work fine. I'm
not familiar with MS C. Does this seem like an OK way to build it?

Are there some SE tests that I should run, or does that fact that it
compiled imply that things are OK?

[Daniel F Moisset]

Post by Grant Rettke
Hi,
I just successfully build SE 1.2r6 on Windows XP Pro by performing the
following
steps (and I've got a question).
Downloaded install.exe and SmartEiffel-1.2r6.tar.
Extracted the tar to c:\ and copied the install.exe into
that directory.
SMARTEIFFELDIR=C:\SmartEiffel12
SMARTEIFFELDIRECTORY=c:\SmartEiffel12
SMARTEIFFEL=%SMARTEIFFELDIR%\sys\system.se
Added the se bin dir for the path.

In theroy, you should not need setting these environment variables

Post by Grant Rettke
Went to dos
Ran vcvars32.bat for the VC++ 2003 Toolkit
set INCLUDE=%INCLUDE%;C:\Program Files\Microsoft Visual Studio
8\VC\PlatformSDK\Include
set LIB=%LIB%;C:\Program Files\Microsoft Visual Studio 8\VC\lib
ran install.exe and chose defaults and then 'cl'.
Here is the question. I used VC++ 2003 to compile the app, but I ended
up using libraries and headers from VC++ 2005. Everything seemed to
work fine. I ran the pretty printer and that seemed to work fine. I'm
not familiar with MS C. Does this seem like an OK way to build it?
Are there some SE tests that I should run, or does that fact that it
compiled imply that things are OK?

If it installs it means that it is compiling quite well (enough to
compile itself and some tools). There is alse a test suite available
from SVN, that runs some small tests (mainly regression), and checks
that gobo and SE1.1 can be compiled (to try to ensure some degree of
backward compatibility).

More info at:
https://opensvn.csie.org/traccgi/smarteiffel12/trac.cgi/wiki/TestSuite

Hopefully, some changes I am introducing at r7 will make it directly
compilable with VC2005

Regards,
Daniel

[Grant Rettke]

Post by Daniel F Moisset
Hopefully, some changes I am introducing at r7 will make it directly
compilable with VC2005

Thanks for the update. That sounds great.

[Daniel F Moisset]

Post by Grant Rettke

Post by Daniel F Moisset
Hopefully, some changes I am introducing at r7 will make it directly
compilable with VC2005

Thanks for the update. That sounds great.

I worked based on your comments; however i have not VC 2005 to test it,
so please report your results.

Thanks,
Daniel