In message <[email protected]> Amin Kharchi <[email protected]> wrote:
> 2. I want to compile files with the postfix .cpp and not .cc. But if I > put the helloworld file in a "cpp" directory, the compiler tells me: > > GCCbin:g++: test/cpp: No such file or directory > GCCbin:g++: no input files > > I assume the cpp-postfix is not supported by the GCC port? Is this a bug > or not provided? .cpp is widely used beside .cc on other platforms. Is > it possible to provide it on RISC OS' g++? The .cpp extension is supposed to be recognized because it is in the UnixEnv$g++$sfix list (see !GCC.!Run). However, to due a couple of bug reports just after release 1, I added an "Alias$g++" workaround in the !Run file in the updates for release 1 which makes that UnixEnv$g++$sfix is not used and the default UnixLib sfix list is used. And that contains .cc but not the .cpp extension. The good news is that we have a proper fix for the problem I'm talking about so the next release won't have that Alias workaround anymore, nor the extension problem it introduced. If you can't wait for that release, feel free to try out to do an "Unset Alias$g++" and see if g++ works, if so, .cpp extension will be supported. The Alias workaround is not needed for sufficent recent versions of RISC OS 4 (not all) and 6, hence that's why I didn't notice this. John. -- John Tytgat, in his comfy chair at home BASS [email protected] ARM powered, RISC OS driven _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
