Permanent Environment for SDK

Hi,
now I'm testing my SDK installation. When I do like recommended on eiffel page with
cmd.exe /V:ON /E:ON./K "C:program filesMicrosoft SDKs Windowsv6.1binsetenv.cmd" /Release
I get a command shell. In it I've started nmake in a simple c example. I get a LH subfolder, where I can find the .obj and .exe file. Ok. This only works in the described instance of the command shell, after leaving it, the environment is lost. But I think Eiffel will need a permanent configured environment.
May be, most of you use SDK and Visual Studio and there is another configuration method or the setenv.cmd file has changed from version v6.0 to v6.1. I havent got VS.
Do I Cannot use the file, should I type in the needed SDK environment?
Now I understand, why Eiffel don't detect the MSC.
Tips will be helpful
Regards
Heiko

[Non-text portions of this message have been removed]

Messages in this topic (1) Reply (via web post) | Start a new topic

.

To use EiffelStudio 6.x with the latest SDK, you need to launch EiffelStudio
from the command shell of the Microsoft SDK that way EiffelStudio should be
able to launch the C compilation since it will assume it is in the path.

The reason is that EiffelStudio 6.x can detect the SDK v6.0 but doesn't know
yet about SDK v6.1. The final release of EiffelStudio 6.2 will know about
the latest versions.

Hope this helps,
Manu

> -----Original Message-----
> From: eiffel_software%40yahoogroups.com">eiffel_softwareyahoogroups.com
> [mailto: eiffel_software%40yahoogroups.com">eiffel_softwareyahoogroups.com] On Behalf Of Heiko Gering
> Sent: Wednesday, March 12, 2008 9:19 AM
> To: eiffel_software
>; Subject: [eiffel_software] Permanent Environment for SDK
>
> Hi,
> now I'm testing my SDK installation. When I do like
> recommended on eiffel page with cmd.exe /V:ON /E:ON./K
> "C:program filesMicrosoft SDKs
> Windowsv6.1binsetenv.cmd" /Release I get a command shell.
> In it I've started nmake in a simple c example. I get a LH
> subfolder, where I can find the .obj and .exe file. Ok. This
> only works in the described instance of the command shell,
> after leaving it, the environment is lost. But I think Eiffel
> will need a permanent configured environment.
> May be, most of you use SDK and Visual Studio and there is
> another configuration method or the setenv.cmd file has
> changed from version v6.0 to v6.1. I havent got VS.
> Do I Cannot use the file, should I type in the needed SDK environment?
> Now I understand, why Eiffel don't detect the MSC.
>; Tips will be helpful
> Regards
> Heiko
>
> [Non-text portions of this message have been removed]
>
>
>
>
> Yahoo! Groups Links
>
>
>
>

Messages in this topic (2) Reply (via web post) | Start a new topic

.

Hi Manu,
thanks for your clarifying words. My last question in this case is, how can I install a working Eiffelstudio, if possible without using mingW. I've overlooked my last mails and think, that SDK installation has something changed on my system (registry?) so that I got the heap error from mingW, with and without installed SDK.

Thank you
Heiko

----- Original Message -----
From: Emmanuel Stapf [ES]
To: eiffel_software%40yahoogroups.com">eiffel_softwareyahoogroups.com
Sent: Wednesday, March 12, 2008 5:33 PM
Subject: RE: [eiffel_software] Permanent Environment for SDK

To use EiffelStudio 6.x with the latest SDK, you need to launch EiffelStudio
from the command shell of the Microsoft SDK that way EiffelStudio should be
able to launch the C compilation since it will assume it is in the path.

The reason is that EiffelStudio 6.x can detect the SDK v6.0 but doesn't know
yet about SDK v6.1. The final release of EiffelStudio 6.2 will know about
the latest versions.

Hope this helps,
Manu

Recent Activity
a.. 2New Members
Visit Your Group
Yahoo! Finance
It's NowPersonal

Guides, news,

advice & more.

Need traffic?
Drive customers

With search ads

on Yahoo!

Cat Groups
on Yahoo! Groups

Share pictures &

stories about cats.
.

[Non-text portions of this message have been removed]

Messages in this topic (3) Reply (via web post) | Start a new topic

.

> thanks for your clarifying words. My last question in this
> case is, how can I install a working Eiffelstudio, if
> possible without using mingW. I've overlooked my last mails

Actually your setup is working just fine and you can go ahead using it.

I finally managed to understand what the GCC problem is and when it occurs.
Can you confirm my findings? Basically I found that `make.exe' fails when
building the missing precompiled library from within EiffelStudio when you
first compile a project. It seems to be an issue with the way the output
redirection is being done for that particular part. We are going to look at
why it fails under this configuration.

The solution I have for you is:
1- build the precompiled manually from within EiffelStudio
2- remove the use of precompiled library from your project settings

For #1, fire up EiffelStudio, and select `Add Project' to add the project
located at $ISE_EIFFEL/precomp/spec/$ISE_PLATFORM/base.ecf and choose
`Precompile' in the `Action' drop down box. You may have to do that for
`wel.ecf' and `vision2.ecf' depending on what you are precompiling.

For #2, fire up EiffelStudio, select `Add Project' to load your project and
then choose `Edit Project'. Within the project settings dialog, go to
`Target: ..' -> `Groups' and remove the precompiled library.

Hope this is helpful,
Manu

Messages in this topic (4) Reply (via web post) | Start a new topic

.

"Heiko Gering&quot; < heiko.gering%40gmx.de">heiko.geringgmx.de&gt; writes:

> Hi Manu,
&gt; thanks for your clarifying words. My last question in this case is, how can I install
> a working Eiffelstudio, if possible without using mingW. I've overlooked my last mails
&gt; and think, that SDK installation has something changed on my system (registry?) so
> that I got the heap error from mingW, with and without installed
> SDK.

> Thank you
> Heiko
Yes you can add the SDK stuff into you environmeent there is a batch
skript setenv.bat, this does changes to you current environment. And
that's what I meant you have to start the installation from an
environment in which all this things are set. It's quite logic if you
have an idea on how this things work, otherwise such "suprises" happen
to you.

Have a nice day
Friedrich

--
Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim
Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

Messages in this topic (5) Reply (via web post) | Start a new topic

.

Hi Friedrich,
I've only found the setenv.cmd file in the SDKs folder. But the execution of this only works in the SDK command shell. Then the environment is set only for this instance of this shell and will be lost after leaving it.

Regards
Heiko
----- Original Message -----
From: Friedrich Dominicus
To: eiffel_software%40yahoogroups.com">eiffel_softwareyahoogroups.com
Sent: Thursday, March 13, 2008 8:00 AM
Subject: Re: [eiffel_software] Permanent Environment for SDK

&quot;Heiko Gering&quot; < heiko.gering%40gmx.de">heiko.geringgmx.de&gt; writes:

> Hi Manu,
> thanks for your clarifying words. My last question in this case is, how can I install
> a working Eiffelstudio, if possible without using mingW. I've overlooked my last mails
> and think, that SDK installation has something changed on my system (registry?) so
> that I got the heap error from mingW, with and without installed
> SDK.

> Thank you
> Heiko
Yes you can add the SDK stuff into you environmeent there is a batch
skript setenv.bat, this does changes to you current environment. And
that's what I meant you have to start the installation from an
environment in which all this things are set. It's quite logic if you
have an idea on how this things work, otherwise such "suprises" happen
to you.

Have a nice day
Friedrich

--
Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim
Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

----------------------------------------------------------

No virus found in this incoming message.
Checked by AVG.
Version: 7.5.518 / Virus Database: 269.21.7/1325 - Release Date: 11.03.2008 13:41

[Non-text portions of this message have been removed]

Messages in this topic (6) Reply (via web post) | Start a new topic

.

"Heiko Gering&quot; < heiko.gering%40gmx.de">heiko.geringgmx.de&gt; writes:

> Hi Friedrich,
> I've only found the setenv.cmd file in the SDKs folder. But the execution of this only
>; works in the SDK command shell. Then the environment is set only for this instance of
> this shell and will be lost after leaving it.
I doubt that it just'll work in a SDK command shell, I guess it will
be possible just to open a command line, run this file and then start
ISE, I bet one can combine it. you "just" have to checkt he whole docs
on how to make the changes permanent....

Good luck
Friedrich

--
Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim
Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

Messages in this topic (7) Reply (via web post) | Start a new topic

.

Hi Manu,
&gt;The solution I have for you is:
>1- build the precompiled manually from within EiffelStudio
already on this step the C compiler crashes. See the message:

Preparing C compilation...
AllocationBase 0x0, BaseAddress 0x715B0000, RegionSize 0x150000, State 0x10000
E:Eiffel SoftwareEiffelStudio 6.1 GPLgccwindowsmsys1.0binmake.exe: *** Couldn't reserve space for cygwin's heap, Win32 error 0

Something like this I've expected, cause this was the problem at all my last tests. The C compiler crashes! More tips will be helpfull, I'll now check the message from Friedrich

Regards
Heiko

PS: This is the environment within the Eiffelstudio console:

$VE_Lib=E:Object ToolsVisual Eiffellib
ALLUSERSPROFILE=C:ProgramData
APPDATA=C:UsersHgAppDataRoaming
CommonProgramFiles=C:Program FilesCommon Files
COMPUTERNAME=HG2
ComSpec=C:Windowssystem32cmd.exe
FP_NO_HOST_CHECK=NO
GOBO_CC=bcb
HOMEDRIVE=C:
HOMEPATH=UsersHg
ISE_C_COMPILER=mingw
ISE_EIFFEL=E:Eiffel SoftwareEiffelStudio 6.1 GPL
ISE_LIBRARY=E:Eiffel SoftwareEiffelStudio 6.1 GPL
ISE_PLATFORM=windows
ISE_PRECOMP=E:Eiffel SoftwareEiffelStudio 6.1 GPLprecompspecwindows
LOCALAPPDATA=C:UsersHgAppDataLocal
LOGONSERVER=\HG2
NUMBER_OF_PROCESSORS=2
OS=Windows_NT
Path=E:C:Windowssystem32;C:Windows;C:windowsSystem32Wbem;C:PROGRA~1COMMON~1ULEADS~1MPEG;C:Windowssystem32;E:Object ToolsVisual Eiffelbin;
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 14 Stepping 12, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0e0c
ProgramData=C:ProgramData
ProgramFiles=C:Program Files
PROMPT=$P$G
PUBLIC=C:UsersPublic
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:Windows
TEMP=C:UsersHgAppDataLocalTemp
TMP=C:UsersHgAppDataLocalTemp
USERDOMAIN=HG2
USERNAME=Hg
USERPROFILE=C:UsersHg
windir=C:Windows

[Non-text portions of this message have been removed]

Messages in this topic (8) Reply (via web post) | Start a new topic

.

Heiko Gering wrote:

>>The solution I have for you is:
>>1- build the precompiled manually from within EiffelStudio
> already on this step the C compiler crashes...
> PS: This is the environment within the Eiffelstudio console: ...
> ISE_C_COMPILER=mingw

Weren't you trying to use the msc compiler?

- Peter Gummer

Messages in this topic (9) Reply (via web post) | Start a new topic

.

----- Original Message -----
From: Peter Gummer
To: eiffel_software%40yahoogroups.com">eiffel_softwareyahoogroups.com
Sent: Thursday, March 13, 2008 10:26 AM
Subject: Re: [eiffel_software] Permanent Environment for SDK

Heiko Gering wrote:

>>The solution I have for you is:
>>1- build the precompiled manually from within EiffelStudio
> already on this step the C compiler crashes...
> PS: This is the environment within the Eiffelstudio console: ...
> ISE_C_COMPILER=mingw
Peter wrote:
&gt;Weren't you trying to use the msc compiler?

Sorry Peter, it seeems that I'm a little bit confused now. Cause installing
Eiffel Studio only works with gcc, I've forgotten about the advices from
Manu before.
Now I've precompiled 2 libraries and my own project!
Thanks a lot to all of you!
Here are the steps I've done:
Environment: ISE_C_COMPILER=msc
launch SDK's cmd shell
typed in setenv /release
typed in $pathestudio.exe
After launching Eiffel Studio, I did like Manu wrote.
Now I'm happy, it was a great support!

Regards
Heiko

Messages in this topic (10) Reply (via web post) | Start a new topic

.