Recent Posts

Pages: 1 2 3 4 [5] 6 7 8 9 10
41
Quote
"FILE-NAME.EXE HAS STOPPED WORKING"
This simply means you have an error in your code. No code error, but a logic error. You have to debug yourself and look where it crashes... Search on youtube/google how to debug your program with codeblocks...
You do not give as nearly enough information to help you more, and even if you give, this is probably the wrong forum to ask this kind of questions
42
I am using Code::Blocks 17.12 and I am using it for writing Codes of C/C++.


currently I am facing an Issue when I am writing C Code in Code::Blocks.


I've 133 Line of C Language Code, when I am Building & Compiling the Code, it shows Black Screen (Command Line Interface) it ask for Input but after that it shows error like "FILE-NAME.EXE HAS STOPPED WORKING".


I don't understand why this gives an Error ?


please anyone can suggest me or help to why this Error is occurring during Output ?


waiting for your valuable reply,
43
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by dhavalveera on August 21, 2019, 03:32:32 am »
here I am
44
Development / Re: Compiling SpellChecker on linux
« Last post by BlueHazzard on August 20, 2019, 09:42:32 pm »
@Obfuscated: can you test the patch on your system and tell me if it compiles? So i can close this...
45
Nightly builds / Re: The 07 August 2019 build (11825) is out.
« Last post by Krice on August 20, 2019, 08:57:04 pm »
OS X version of this rev can be downloaded

Does OSX version need some kind of modification to work properly? I can't make it work when I build from source. It doesn't find a compiler and plugin directories are empty, although the directory structure is made under Users/(user)/Library/...
46
General (but related to Code::Blocks) / Re: CodeBlocks with wxWidgets compiler failed.
« Last post by sodev on August 20, 2019, 07:51:48 pm »
I would try building using SHARED=0 MONOLITHIC=0 in a new build location.
The combination of SHARED=0 and MONOLITHIC=1 is almost never used; so, it is more likely to be broken in wxWidgets or Code::Blocks.

I can't agree with that, in fact SHARED=0 MONOLITHIC=0 doesn't buy you anything, you are linking statically, unused stuff doesn't get included anyway, its just easier to link with one library in that case. Non-monolithic builds make more sense when using shared libraries, in this case you can skip linking the libraries you don't need so you can reduce the required external dependencies the unused libraries depend on.
47
And you have no other compiler installed? or in the path?

Thanks, it is this problem.

On my computer installed perl, perl has gcc.
I remove perl in system path, and rebuild wxWidgets, now everything is fine.
48
Please add the "-v" to your project build options:
Project->Build options->Compiler settings->Other compiler options
and
Project->Build options->Linker settings-> Other linker options

now make a rebuild by hitting the blue arrows or Build->rebuild

In the build log it should now tell you what libraries it tryst and the reason why they are rejected by the linker.
Pleas post the build log of the rebuild.

Thnak you
50
After you try every thing else.

Code: [Select]
mingw32-make -f makefile.gcc SHARED=0 MONOLITHIC=1

I would try building using SHARED=0 MONOLITHIC=0 in a new build location.
The combination of SHARED=0 and MONOLITHIC=1 is almost never used; so, it is more likely to be broken in wxWidgets or Code::Blocks.

NOTE: You must build in a new location changing the value of MONOLITHIC in the same location results in a broken wxWidgets build!

Tim S.

Pages: 1 2 3 4 [5] 6 7 8 9 10