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

gcc-4.6.1 builds availiable

<< < (8/8)

reckless:
Ok big fat readme at the bottom of the files page, and i started reordering things a bit.
Ill update the readme with new additions.
Uploading select packages to there respective folders now.
SoftWare Development Kits will contain things like IrrLicht and Ogre Sdk's and the file ending will contain 32 or 64 to point out which architecture it was build for.
Tools Will be for general use. Ill Probably add stuff like My MinGW python to this.
Msys Specific will be for Msys tools And Libraries.
Sources Will Contain My ported sources.

uploading things now.

reckless:
Am i that hard to read ?.  Sorry about that, ill see if i can write a bit cleaner, but english is not my native language either.
It is not 1 GB anymore, im removing that package as it seems to confuse people. The new package is about 360 mb still big but im working on stripping everything to the bone,
so i might be able to squash its size a little more. Everything that was in the old package will be uploaded as seperate packages.

And sorry for the offtopic stuff its not exactly related to C::B itself. I just wanted to create something as ready to go as possible for people not used to working with a gcc compiler.

Dreamy:
Okey, I've read whole thread and it really needs to be a crypto analyst to extract a simple "what the hell is this":

Hello, I'm XY
and I'm trying to do XY,
I believe it's gonna be really useful for XY.

Until now, I've done:
- this
- this
- and this

And if I do:
- this
- this
- and this

It's gonna be the best stuff ever.


So if you say I just wanted to create something as ready to go as possible for people not used to working with a gcc compiler, I am pretty sure those people would love an introduction like this.

P.S.: Is this thread in right category?

reckless:
I think the message came through that i need to be a little more clear.
In short it was an attempt to make an easy to use package for the MinGW64 compilers with C::B,
plus a posix shell environment with some otherwise not to easy things allready setup for use.

Question.
So why would i need Msys for C::B ?.
A: Because many tools and libraries you might need dont have a C::B workspace.
B: To port something from say linux to windows, and use it in your application.
C: Because one of the tools you intend to use needs a posix shell.

Hmm might be usefull.

Answer.
A: I only use windows libraries or tools ported from msvc.
B: see A.
C: I dont use scripts and/or autotools again see A.

Cool go ahead and use the normal distribution :) .

Navigation

[0] Message Index

[*] Previous page