ext compilation error

[r...@amalasoft.com]

Any hints?

Nearly at the end of C compilation (but not _at_ the end, there is this error.  v 19.05

"C:\Program Files\Eiffel Software\EiffelStudio 19.05 GPL/gcc/win64/mingw/bin/ld" -r -o Cobj9.o big_file_C9_c.o 

c:\Program Files\Eiffel Software\EiffelStudio 19.05 GPL\gcc\win64\mingw\bin\windres.exe: no resources

make.exe": *** [ds_test.res] Error 1

make.exe": *** Waiting for unfinished jobs....

The classes being compiled have no GUI components; just data structures and console output.

There are the usual number of C files in the the C9 directory, and their aggregate size is just under 2M (smaller than some of the others)

R

[r...@amalasoft.com]

OK, I'll offer one of my own.

Looking around for anything "resource" related, I discovered that the ds_test.rc file in the project directory was empty.  I then compared it to another (newer) project's .rc file and found that the newer project's file actually had some content.  So, I copied that file and renamed it and Voila!  The project compiled (after a good cleaning).

This discovery led to another point of confusion.  The resource file (the non-empty one I copied) had the following content:

>>>>>

#include <windows.h>

STRINGTABLE
BEGIN
1 "This Program was made using EiffelStudio using Visual Studio C++"
END
<<<<<

Problem is, I'm using mingw, not VC++ in both projects.  So, the question arises "Is is OK to lie about the C compiler?"

R

--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/20210401065146.cf48dd763fcaf5d42559c6c92f6fc53b.8526938631.wbe%40email25.godaddy.com.

[Jocelyn Fiat]

Hi,

I have just tried again to use mingw, and for me the generated file .rc contains something like "This Program was made using EiffelStudio using GCC"

in fact, the .rc is generated using the %ISE_EIFFEL%\studio\config\win64\mingw\eiffel.rc

Then I guess, the .rc file you have is from a previous compilation, using VisualStudio  (i.c ISE_C_COMPILER=msc or msc_vc140  (for GCC, it should be ISE_C_COMPILER=mingw)

Or the .rc file was saved in your repository.

Please let us know if my guess is correct. If it is wrong, could you tell us more and how to reproduce this issue?

Regards,

-- Jocelyn

To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/20210401145202.cf48dd763fcaf5d42559c6c92f6fc53b.12902be663.wbe%40email25.godaddy.com.

--

Jocelyn
------------------------------------------------------------------------
Eiffel Software
https://www.eiffel.com
Customer support: https://support.eiffel.com
User group: https://groups.google.com/forum/#!forum/eiffel-users
------------------------------------------------------------------------

[r...@amalasoft.com]

Hi Jocelyn

It's a bit late to check the times on the rc files in question (I should have done that before).  My guess is that, yet, the file in question is a leftover, BUT, all this trouble began when my old system's motherboard went South and I had to build a new system from the rubble.  I tried all kinds of combos and I certainly could have left an invalid rc file laying about because I copied a lot of content from the old hard drive.

There is no env variable for ISE_C_COMPILER, but again it might have been picked up before.

Having the initial attempt at compilation fail due to a missing rc file seems like the actual problem.  It strikes me that it should be generated automatically if it's not present.

I'll keep my eyes open for other strangeness.

Thanks

R

To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/CAFq%2Bd47v-vNDS0QBd7hXvTXsMFr8Gn%2BcqvWyZSxo2ccDKZQiCA%40mail.gmail.com.