News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Problem with mising dll

Started by gtafan, July 12, 2020, 08:31:54 PM

Previous topic - Next topic

gtafan

Have instaled the latest version of CB but when starting always geting mesage about some mising dll. Umfortunately this forum is not worcking on normal PC, so can't post the exact error mesage. Google seatch said it some of visual sh*t dlls, so I think no need to mention what my OS is.

stahta01

What OS version? Include 32 or 64 bit information!

Tim S.
C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]

gtafan

Win 7 pro 64 bit, but CB is 32 bit. All previous CB versions were 32 bit to and worcked perfectly on this OS.

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

gtafan

Quote from: oBFusCATed on July 13, 2020, 10:23:34 PM
32bit version is known to be problematic.
http://forums.next.codeblocks.org/index.php/topic,23770.msg162098.html#msg162098
OK, looks like the problem, mentioned in that thread, is exact the same as mine. Since my OS is 64 bit should be no problem fro me to use 64 bit CB version. Posibly a stupied question, will I be still able to compile 32 bit applications with 64 bit version?

sodev

This does not depend on CodeBlocks but on the used compiler. If you intent to use CodeBlocks with the bundled compiler it is important to know that MinGW-w64 is not multilib. I guess the 64 Bit download contains a 64 Bit toolchain so this one can't build for 32 Bit, in that case you need to install a 32 Bit toolchain yourself.

oBFusCATed

Quote from: gtafan on July 20, 2020, 12:37:57 PM
OK, looks like the problem, mentioned in that thread, is exact the same as mine. Since my OS is 64 bit should be no problem fro me to use 64 bit CB version. Posibly a stupied question, will I be still able to compile 32 bit applications with 64 bit version?
Yes, but debugging would be close to impossible.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

nenin

Quote from: oBFusCATed on July 20, 2020, 07:47:36 PM
Quote from: gtafan on July 20, 2020, 12:37:57 PM
OK, looks like the problem, mentioned in that thread, is exact the same as mine. Since my OS is 64 bit should be no problem fro me to use 64 bit CB version. Posibly a stupied question, will I be still able to compile 32 bit applications with 64 bit version?
Yes, but debugging would be close to impossible.
For me it is working. I have "cocktail" of 64b CB, 32b gcc 9.2 from Winlibs and TDMs 32b GDB.

oBFusCATed

Try to set a breakpoint while the application is running - it should fail :)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

gtafan

Quote from: oBFusCATed on July 20, 2020, 07:47:36 PM
Quote from: gtafan on July 20, 2020, 12:37:57 PM
OK, looks like the problem, mentioned in that thread, is exact the same as mine. Since my OS is 64 bit should be no problem fro me to use 64 bit CB version. Posibly a stupied question, will I be still able to compile 32 bit applications with 64 bit version?
Yes, but debugging would be close to impossible.
I don“t care about debugging, as long I can produce a 32 bit executable.

nenin

Quote from: oBFusCATed on July 23, 2020, 02:21:31 AM
Try to set a breakpoint while the application is running - it should fail :)
I had to live like this for years and now I did not even recognize that it is a problem.  ::)
I'll check behavior at Monday.

gtafan

An other posibly stupied question, at the moment I am still using version 17 with compiler that has no problem to produce 32 bit executables, can I just instal the new CB version over the old one, so it uses the worcking compiler?

Miguel Gimenez

If the compiler was installed with C::B then the 17.12 uninstaller could possibly remove the MinGW installation (I do not use the installer).

I would download the last nightly and put it over the 17.12 installation, it has some advantages over the 20.03 release and it will use your existing compiler.

gtafan

Quote from: Miguel Gimenez on July 27, 2020, 01:36:52 PM
If the compiler was installed with C::B then the 17.12 uninstaller could possibly remove the MinGW installation (I do not use the installer).

I would download the last nightly and put it over the 17.12 installation, it has some advantages over the 20.03 release and it will use your existing compiler.
Would really like to stay with the release version. So if I understood you right, installing 20.03 would automaticaly uninstall the previous version including everything installed with it like compiler? The result would be version 20.03 without any compiler, right?

Miguel Gimenez

Well, I wrote "could possibly remove". I don't use the installer, so I don't know if it uninstalls the previous version or it just overwrites it.
Looking at the nsi files, I think uninstallation removes C::B and the compiler, and installation overwrites C::B previous files without uninstalling anything, but I can be completely wrong.

https://sourceforge.net/p/codeblocks/code/HEAD/tree/setup/setup_wx31_32bit.nsi