Unable to compile C++

[idcarlos]

Hi.
I have instaled CB and C programs works OK

But when I try to make a build of a C++ code I see this:

Project   : WPM_GLADE
Compiler  : GNU GCC Compiler (called directly)
Directory : D:\CodeBlocks\WPM_GLADE\devcpp\
--------------------------------------------------------------------------------
Compiling: ..\src\main.cpp
mingw32-g++.exe: no input files
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings

Why?
..\src\main.cpp it's ok and point to the correct path (D:\CodeBlocks\WPM_GLADE\src\)

[Michael]

Hello,

It is strange. With me it works fine.

Which version of C::B are you using? And which GCC version?

Best wishes,
Michael

[idcarlos]

CB 1 RC2

GCC is 3.4.4
24/05/2005  01:00            90.624 mingw32-g++.exe

[Michael]

Ok, so you probably downloaded RC with MinGW bundled.

My advice would be to install MinGW 5.0.2 (eventually update it the new winapi32 and binutils header files. And may be with GCC 3.4.5). Then download the latest nightly build and install it. Nightly builds are much better as RC2 and quite stable (IMHO as stable as RC2 ).

Best wishes,
Michael

[idcarlos]

Nightly builds are easy to update?
-Have diffs or I need entire CB?
-Install or only replace files?

In only 1 hour I have found some problems... ¿People use CB on windows or is focused for Linux?

[killerbot]

really simple, do not mix with rc2 though : nightlies can overwrite each other

[Michael]

Nightly builds are easy to update?
-Have diffs or I need entire CB?
-Install or only replace files?

Nightly builds are easy to install. Just download it with the libraries you eventually need, unpack and run. Personally, I prefer to build it myself from SVN sources. You can post, if you have problems.

In only 1 hour I have found some problems... ¿People use CB on windows or is focused for Linux?

C::B is still in development. Anyway, it works very good and it is stable.

About Linux and Windows, it is a bit difficult to say. I would say that most of the users that use C::B have Windows XP (some Windows 2000/NT or Win98SE). Anyway, there is good number of Linux users too. And some with MacOSX...

C::B is cross-platform, so you can build and use it in Windows, Linux and MacOSX.

Best wishes,
Michael

[Michael]

though : nightlies can overwrite each other

Hmmm, I was not aware that with nightly builds this was possible.... :?

Ok, I will change my post .

Best wishes,
Michael

[killerbot]

I mean : you can unpack them on top of the previous one.
The only time this might be a problem is when a certain plug-in would no longer be included, then the old one will not be overwritten and remaind in your plug-in dir ( and might get out of sync with the sdk).

[idcarlos]

Hi.

I have instaled 28/02/2006 build
All bugs that i have detected are fixed.

The project can't be compiled because I chande the XML file to replace the paths :oops:
I replace something like this

Code (xml) Select Expand

<Add directory='&quot;D:\Archivos de programa\Archivos comunes\GTK\2.0\include\gdkmm-2.4&quot;' />
With

Code (xml) Select Expand

<Add directory="..\..\include\gdkmm-2.4&quot;" />
And the project never work, without a good error msg...

This not it's a bug because I made a bad cbp file, but...
Lines in DEV-cpp like this:
"D:\Archivos de programa\Archivos comunes\GTK\2.0\include\gdkmm-2.4"
Are translated

Code (xml) Select Expand

<Add directory='&quot;D:\Archivos de programa\Archivos comunes\GTK\2.0\include\gdkmm-2.4&quot;' />
Any I thing that It's better

Code (xml) Select Expand

<Add directory="D:\Archivos de programa\Archivos comunes\GTK\2.0\include\gdkmm-2.4" />


   

[thomas]

Once again, I am thinking about encrypting the config file...

[MortenMacFly]

Any I thing that It's better

Code (xml) Select Expand

<Add directory="D:\Archivos de programa\Archivos comunes\GTK\2.0\include\gdkmm-2.4" />

It's not better. Path's with spaces need (!) to be quoted.
Morten.

[MortenMacFly]

Once again, I am thinking about encrypting the config file...

...but with an decryption key for "professionals". :lol:

[rickg22]

I wouldn't recommend encrypting it, it only complicates things.

You could instead, post a comment on the top of the config file and say "do *NOT* modify this file by hand! Manually modified configurations are NOT supported, use at your own risk!"

That ought to scare newbies

[sethjackson]

I wouldn't recommend encrypting it, it only complicates things.

You could instead, post a comment on the top of the config file and say "do *NOT* modify this file by hand! Manually modified configurations are NOT supported, use at your own risk!"

That ought to scare newbies

Yeah.

encryption = bad (in this case)