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

Manual fork of Code::Blocks to improve MSys2 support

<< < (3/3)

WinterMute:

--- Quote from: stahta01 on September 17, 2019, 03:21:53 am ---
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.


--- End quote ---

What are you referring to here? I use C::B in tandem with msys2 quite regularly and all I do is have the build system use msys2 make rather than mingw32-make and everything works fine. I wish people wouldn't use mingw32-make, it's rubbish and misbehaves when sh.exe is in the path.

oBFusCATed:

--- Quote from: stahta01 on September 17, 2019, 03:21:53 am ---I also plan to have the configuration save differently when running in the MSys environment.

--- End quote ---
An elaboration about this topic would be needed. Why do you need a separate config? How are users going to specify that they want to use this separate config file (probably a command line option)?

stahta01:

--- Quote from: oBFusCATed on October 06, 2019, 10:58:52 pm ---
--- Quote from: stahta01 on September 17, 2019, 03:21:53 am ---I also plan to have the configuration save differently when running in the MSys environment.

--- End quote ---
An elaboration about this topic would be needed. Why do you need a separate config? How are users going to specify that they want to use this separate config file (probably a command line option)?

--- End quote ---

When they start the IDE from an MSys2 mingw prompt it uses and saves to under the MSys2 folders.
And, few features are only enabled when running from an MSys2 mingw prompt.

Tim S.
 

Navigation

[0] Message Index

[*] Previous page