Re: Re: Gobo with EiffelStudio 5.4

Peter Gummer <[email protected]>
Newsgroups gmane.comp.lang.eiffel.gobo.general
Message-ID <[email protected]>
On 10/08/2004, at 12:57 PM, Peter Gummer wrote:
>  So at this point, I have got through the Eiffel compilation, but, as I
>  feared, the Borland linker has 'unresolved external' errors on all of 
> the
>  ECLI stuff that I compiled yesterday with Microsoft C.

And I now have the EPOM example running. The "unresolved externals" 
were fixed by adding external references via EiffelStudio's Project 
Settings. I also had to build two ECLI DLLs with Borland C. I finished 
up doing so by running make directly, not by running geant which as far 
as I can tell just made it more complicated, not simpler as it 
supposedly should.

In fact, the whole geant/gexace thing just turned out to be a useless 
distraction, as far as I can tell. The only thing I finished up using 
them for was when I manually read an xace file in order to work out 
which ODBC DLL to use. This was a minor benefit, as I probably would 
have figured this out almost as easily just by looking for DLLs in the 
Borland compiler's subdirectories.

Anyway, now that I've done this manually, if there is good advice on 
how to do it better I'd still be interested.

- Peter Gummer




------------------------ Yahoo! Groups Sponsor --------------------~--> 
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/saFolB/TM
--------------------------------------------------------------------~-> 

To Post a message, send it to:   [email protected]
To Unsubscribe, send a blank message to: [email protected] 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/gobo-eiffel/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.