Win32 with Mingw

[ajtribick]

Still way over my head.
It is for reasons like these that I like working examples of a compiler with a project.
Were I not doing this as a favor or for pay I would have long since walked away.

Well you've automatically made it harder for yourself by going for a compiler that we don't support yet. Yes I want to get MinGW up and running but this is not yet part of the codebase. Sorry but if you are going to put anti-MS ideology as your overriding concern as you appear to be doing, you're going to have to expect you're going to have to be prepared to put up with a few problems.

[ajtribick]

Furthermore I don't know what you're doing here to build it.

This is the process I used:

Check out the Celestia trunk
Apply the patch.
Get MinGW, ensure everything is up-to-date.
Add the MinGW bin directory (C:\MinGW\bin) to your System path.
Get the Qt SDK from here
Use the Qt 4.8.0 for Desktop (MinGW) shortcut created in the start menu to launch the command line. (NOT the MinGW shell.)
cd to the src directory in the Celestia folder

Then execute the following:

qmake -spec win32-g++ celestia.pro
mingw32-make release

[John Van Vliet]

--- edit ---

[Doors]

Still way over my head.
It is for reasons like these that I like working examples of a compiler with a project.
Were I not doing this as a favor or for pay I would have long since walked away.

Well you've automatically made it harder for yourself by going for a compiler that we don't support yet. Yes I want to get MinGW up and running but this is not yet part of the codebase. Sorry but if you are going to put anti-MS ideology as your overriding concern as you appear to be doing, you're going to have to expect you're going to have to be prepared to put up with a few problems.

Such is life.
I have many problems. I am not rich, I have to work, it happens.
I also happen to be bad at putting things into words, so apologies if I seem mad or something else, I am not, I am frustrated.
The same thing that helps me be good at one type of things, makes me bad at others.

I had not realized that mingw had to be separated from the cygwin stuff.
The only difference I knew of was no dependence on cygwin dlls.
My understanding was that cygwin stuff would compile on mingw by simply running configure then make.

I normally work at the hardware and cpu register level.
I prefer embedded work, repetitive, but predictable.
In it, using black box libraries only breaks things randomly instead of predictably.
I have fought serial Vs Ethernet libraries before where both wanted to use the same fifo.
Turned out, after disassembly of course, that the ethernet one contained fall back code to the serial and always assumed it would do the serial.
The library maker hadn't documented that though.
So I trimmed out the offending code, saving a full K of rom space, and everything worked fine.
This is why I want what I want.
I am sticking to what I know I can do.
Putting a compiler in my main path always causes me problems, so I always prefer portable to installed.
Thus my preference for mingw which doesn't use the regsitry, to cygwin which does and requires the cygwin dll.

As for my anti MS preference.
I don't like them, I use windows because it is the most adaptable for my requirements.
I stopped at XP, Vista is feces and 7 is just garbage to my eyes. (Personal preference, for those that like or prefer them, please, feel free, enjoy.)
Linux is getting better, but keeps doing things like gnome3, and I have trouble finding things that are by logic related, like screen resolution, desktop icon size, color correction, etc, but are in random places that make no sense to me.
Others like it, have fun, enjoy.
I don't use mac, have never used mac, and don't even anticipate using mac.
They don't work for me, they do for others, please, enjoy if it does.

My rant if you will, is that I dislike visual languages.
I dislike VS and Delphi and Lazurus and code blocks and all the rest I have seen.
This is MY preference, there is nothing inherently wrong with any of those, I just don't like them.
I can't track anything coherently on them, which is the same problem I have with most modern programs.
Ribbon interfaces drive me nuts, the propensity of tool bars as blocks I can't turn of individual buttons in is just as bad.
It is easier for me to go through the few hundred buttons and select the few I want than to figure out where they hid them.
What is related to me is not to them, what is related to them is not to me.

So, yes, I know my preferences will create problems for me.
And yes, they are my problems.
If I offend someone, please accept my apologies, none is intended.

Doors.

[Doors]

Furthermore I don't know what you're doing here to build it.

This is the process I used:

Check out the Celestia trunk
Apply the patch.
Get MinGW, ensure everything is up-to-date.
Add the MinGW bin directory (C:\MinGW\bin) to your System path.
Get the Qt SDK from here
Use the Qt 4.8.0 for Desktop (MinGW) shortcut created in the start menu to launch the command line. (NOT the MinGW shell.)
cd to the src directory in the Celestia folder

Then execute the following:

qmake -spec win32-g++ celestia.pro
mingw32-make release

Latest attempt.
Grabbed Qtsdk/creator, installed. (1.7Gig)
Took svn, applied archive to update libraries.
Figured out how to use diff/patch, not tools like I have used in my normal work, I also don't do distributed work either, I typically fix things that should have worked or were working, but didn't or now don't, so I have not had any need.
Opened celestia.pro file in qtcreator.
Selected build project celestia.
Selected debug build.
Got warnings for declared but unused var types, ignored.
Got errors for missing __chkstk_ms (in cspice.a I think, only place the filenames showed up in plain text.)
Determined that cspice is not the spice langauge for hardware circuit modelling.
Discovered Nasa spice.

Now have no clue what to do about it.

As for putting anything in my main path, NO.
I have made this mistake before, it ends badly.
If needed I will vbox an OS with it installed. (Annoying, I have space, but it is not unlimited.)
I have a vbox w/VS2K8 express, and another with cygwin, I can copy them, but they are HUGE, MS is a storage hog.
Tried a vbox with ubuntu, ugg, not my speed.
I am currently using it to try to learn fedora, am looking at 13 and 14.
I hacked it to allow root login, it is the way I work and it has no network hookup, besides, hitting su or sudo every time I wanted to do something interesting really got annoying after the twentieth time.
I looked at newer versions of fedora, but the logic of the layout escapes me completely.

I prefer to prepend to the path for the running of a program, it works better for me.

[John Van Vliet]

--- edit ---

[Doors]

Want exe or dll, ZERO interest in unix.

1 . NO mix cygwin/mingw, no problem.

2 . Did that. mingw & gnuwin32/mingw. (both)

3 . Tried to figure it out (both)
3a. Got msys working in mingw. Not able to compile, on me, had trouble figuring out which version of what library to compile --with-glut since I had at least heard of glut before, eventually gave up since I couldn't make the opengl/glut stuff work. Found out later that the non QT stuff is deprecated.
3b. Installed, now what? How do i get a prompt? Where is Msys or equivalent?

4 . Is the list(Specifically for mingw) I followed from a previous post wrong? I installed all those things and still ran into missing libraries referencing files I couldn't find. Installed the QT sdk stuff and tried through it, still no dice. Wants __chkstk_ms from frmchg.c and several more somewhere in cspice.a which I have idea what to do with as of yet.

5 . That is what I am trying to do.

I have tried reading the guides for mingw.
It all seems to be written in some way that is gibberish to me.
I know the limitation is most likely me, I work mostly at the low level and this is high level.
All of the web pages I have found define things in circles or are based on secret understanding I lack.
It is as frustrating to me as the logic behind Unix/Linux, which seems related.
I can find thousands of web pages that outline it, but none that explain why it is the way it is.
I am mostly storage oriented, yet in linux storage seems to be almost an after thought.

Those of you here have many years doing this, I don't.
I don't work by rote, I work by understanding or comprehension.
I have found over time that the easiest way for me to learn something new in computers is start with a known working example, then try to replicate it or break it piece by piece.
I am trying to learn a number of new things all at once here.
I have had some success with mingw before, I hope to replicate it.

I now realize this probably feels like hand holding to you all so I will stop bugging people before I become a pest.
I doubt you understand the gaps left in your efforts to help, the assumptions made about things I will know or do because they are so simple and everyday to you.
When I get a working mingw compiler and working sourcecode (from SVN>5205) ready, I will post it as a working archive along with directions on replicating the steps to get there.
That way the starting bar is lowered for others simply wishing to play or experiment with celestia to try out an idea, but lacking in your years of knowledge and understanding, hopefully providing a newbie friendly path to learning.

Thank you for your efforts.

[duds26]

Doors you can't always know everything.

Your missing understandings seem to be because you don't understand well what the things you are using are or do.