Re: [Dev-C++] Filename case shouldn't matter (overcoming '__gxx_personality_v0')

[Asko K. <ask...@sc...>]

Then at least the error message generated from this should be clearer 
than "__gxx_personality_v0".

Or the project options should allow clearer C/C++ selection. Now the 
wizard actually asks it, but it didn't seem to make much difference 
(since I had "C project" checkbox selected and yet ended up in these 
trouble..)

On the positive side, I got my source C++ qualified... ;)

-ak


Per Westermark kirjoittaa tiistaina, 25. helmikuuta 2003, kello 15:01:

> But on the other hand, that would break all projects where the source 
> is
> shared between Unix and Windows, and where the the .C extension do 
> signify
> c++ files. I would assume that the most logical function is to keep the
> case of the original files.
>
> I have in a number of cases seen DeveloperStudio sometimes naming
> the files in upper case in the project file.
>
> /Per W
>
> On Tue, 25 Feb 2003, Asko Kauppi wrote:
>
>>
>> Hi, all!
>>
>> I moved a project over from VC++ to DevCpp recently and it seems I'm
>> hooked! DevCpp is simpler to use than VC++ and since it's free.. 
>> Great!
>> :)
>>
>> However, there was one big problem trying to get my source compiling 
>> on
>> DevCpp. Or rather, once solved, it was minor.
>>
>> The case of the filenames had changed during transportation so I had
>> 'MYFILE.C' instead of 'myfile.c' (on WinXP Home running under iMac
>> Virtual PC if it matters). Normally, file case does _not_ matter in
>> Windows so I didn't pay attention.
>>
>> Compilation ok, but then I get these 'missing __gxx_personality_v0'
>> linker errors. Why?!?
>>
>> Turns out DevCpp (or rather, gcc) thinks my source is C++ since the
>> extension is an uppercase '.C'.
>> This is utterly confusing to newcomers so my suggestion would be:
>>
>> 	- Always feed Windows filenames to gcc in lowercase. This will make
>> DevCpp behave
>> 	  as Windows people expect, and '.cpp' etc. can still be used for C++
>> source.
>>
>> This way, gcc behaviour itself would not need to be modified, only 
>> your
>> interfacing with it.
>>
>> Any downsides to this suggestion?
>>
>> -ak
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Dev-cpp-users mailing list
>> Dev...@li...
>> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
>> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>>
>