Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Manual fork of Code::Blocks to improve MSys2 support

<< < (2/3) > >>

ollydbg:

--- Quote from: oBFusCATed on September 15, 2019, 11:18:42 pm ---What do you mean by HUGE?
To develop for Windows you have to target win32 API or whatever is modern now.
How Msys2 helps with that? If you don't want to target Windows native APIs, but won't to target some posix thing, why don't you develop on the posix thing (linux, *bsd, macOS, etc)?

If you don't target the native APIs your application would be usability disaster...

--- End quote ---
Msys2 supplies three build systems. One is the posix like compiler suite. The other two are the native compiler suites for either 64bit and 32bit. Most people use the later ones and the native libraries.

BlueHazzard:
msys2 gives you a packet manager, and a unified installation structure on windows like on linux. But without using some quirky binary layer like cygwin.

oBFusCATed:
But can I build an app which doesn't depend on msys2 and I can ship it to people?

ollydbg:

--- Quote from: oBFusCATed on September 16, 2019, 07:51:47 pm ---But can I build an app which doesn't depend on msys2 and I can ship it to people?

--- End quote ---
Yes, you can. This is what I do for my project. You just ues the native gcc compiler and libraries supplied by msys2.

stahta01:
I see no reason for the C::B team to supply a separate zip for msys2.
I do plan on providing a couple of zips myself.

The main things I wish to submit patches to C::B for is making the back ticks use the sh.exe when the IDE is ran from under the MSys environment. This will allow many things to work better.
I also plan to have the configuration save differently when running in the MSys environment.

Tim S.

Navigation

[0] Message Index

[#] Next page

[*] Previous page