On 03/27/2012 08:34 PM, Selden E Ball Jr wrote:

According to the Wiki book entry about VS10, one has to make several
changes to files in order to get VS2010 to work with the svn files.
One cannot simply download the svn code and invoke the compiler
as is possible with vs2008. If that is not true, please update
the Wikibook page appropriately.
First +Third point: modification of a couple of directory macros.

This is straightforward, takes a few minutes and is due to the fact that we want the celestia executable located in the celestia root dir rather than in Release/ or Debug/ (the standard MS convention). Without the obvious adaptation of macros, running Celestia.exe from the IDE with CTRL+F5 fails, but starting Celestia via WE still works.

Here are my settings that work without complaints: I compile with F7 and run with CTRL+F5 from the IDE.

General property:
                 Output Directory: $(SolutionDir)
                 Intermediate Dir:  $(Configuration)\
                 Target Name    : $(ProjectName)

Debugging property:
                 Command                  : $(TargetPath)
                 Command Arguments:
                 Working Directory       : $(ProjectDir)

Second point: I have no problems with the static Windows libs from SVN. Besides the full VS 2010 installation, I have the redistributables for VS 2005 and VS 2008 installed, for running various applications that need them (e.g. Maple, Matlab,...). That's easy to do if required. Furthermore, I just checked with the familiar 'depend' tool which modules are linked into my  VS 2010 celestia.exe. I only found msvcp100.dll no earlier versions. Note that there are various incompatible library sets around! I am always referring to the latest set committed by Chris to SVN about 2 years ago. Moreover Andrew now has compiled a new set with VS 2010. I have tested it a few days ago. His new set works as well as the present SVN set. 
Please don't forget that people now expect the Wikibook to
contain the appropriate documentation. 
Right. Unfortunately, significant parts of what you wrote into Wiki during the past days are misleading | incorrect. It would be better to gain some practical experience with the matter before updating the Wiki book ...
My understanding from reading Nokia's Qt download page is that the 
amsll download is just an installer. It then provides a menu of 
many options, which potentially consist of many hundreds of megabytes 
of dditional downloads.
The binary archive I was referring to has 53 MB and the Qt Creator suite (I checked once more!) has 137 MB after unpacking and installation. That is the usual size factor of ~ 2.5 in zip archives. And THAT is PEANUTS. I assure you that the start-up time is no longer than that of e.g. firefox 11.0 which is typically 2-4 seconds. Your statement in Wiki of Qt Creator using /90 secs/ start-up time is misleading and incorrect.

Just download that binary Qt Creator archive yourself and you will see that it only takes < 1 minute. You can't do any harm without installing it. I quote from Nokia

>>The source code is available as a zip (31 MB) or a tar.gz (25 MB).

Obviously, if the zip sources are only 31MB, how can the installed program be 5 GB (!) as you claimed previously??  
They also provide an ISO which seems to be only for Desktop development 
which is more than a GB, and which still needs updates to bring it up 
to the current version. I wasted several days trying to update the
(somewhat older) version that I had.
Because you mistrusted my long experience...;-)
I was never able to reproduce the performance you described
and am much too frustrated with it to be willing to spend more 
days trying -- especially since I have something now
which works fine for my purposes. (Except for Symantec's false
positive. In addition to reporting it to our local support channel,
I used a reporting page on Symantec's Web site. I suspect neither
will result in a fix in the near term, though. In the meantime, I have
selected SEP's "exclude" option which allows Celestia-qt4 to run.)
Note that problem is a rather general one related to SONAR scans. There are NO definite virus signatures to hunt for in this case. Hence many more false positives occur.




On 03/27/2012 07:06 PM, Selden E Ball Jr wrote:

I'll be glad to update the Wiki page when the files in
Celestia's svn repository actually support vs2010.
I am regularly compiling SVN with VS 2010 since ONE year without ever
encountering any version specific problems. (I also have VS 2008 SP1
installed on XP . This allows me to cross-check with VS 2008 any time).

A few days ago Andrew has also succeeded to compile Celestia.SVN  and
the external libs in windows/ with VS 2010. What else do you want?
(Personally, given the likely release schedule for the next
version of Celestia, it seems to me to be more appropriate to update
to VS11, even though it's still in beta. VS11 and Win8 both will be
shipping this autumn. Betas for both are available for free now.)
It is an old rule of experience that one better awaits the SP1 release
with any version by MS.
I'm only willing to document what happened when I tried to use the tools.
If your experiences are different, please feel free to update the
Wikibook appropriately so that others will be able to reproduce your
As I am writing repeatedly, I have documented my results a long time ago
in already
(e.g. in the Qt thread)
while Qt Creator seems to provide significant help for those who prefer
GUI interfaces, I personally find its size (more than 1 GB of initial
download, more than 5GB when installed, plus many hours to update it)
unnecessary for someone who is only interested in bullding from svn.
Wait a second!
According to NOKIA, the /binary/  Qt Creator 2.4.1 download for Windows,

has a size of 53 MB only. It downloads in ~ 30 SECONDS on my machines.
It installs in a VERY short time and only takes 2-4 seconds to start!

When I read your strange  remarks about Qt Creator it sounds as if I was
constantly lying to you ;-)



On 03/27/2012 06:18 PM, Selden E Ball Jr wrote:
I've added a section about using qmake from the Windows command line.

(After managing to get the Qt SDK in a state where it did not build
any runnable executables, I deleted it entirely and started over.)

So at least you seem to agree now that my repeatedly recommended way of
ONLY installing the Qt-libs is much more efficient compared to
installing the huge QtSDK. I really don't understand why in your new
Wiki entry you recommended people to install the old VS 2008 (not even
emphasizing the importance of SP1!) instead of the current and
well-working VS 2010. Once more: unlike VS 2008, the VS 2010 Express SP1
allows for clean 64 bit compilation!
I suppose you read in the recent discussions between Andrew and myself
that we are planning to update the whole SVN build process for Windows
to the VS 2010 level. Since building with VS 2010 works perfectly at
least since ONE year already, there is little reason, indeed, to suggest
users to install the old VS 2008 at this time.
Moreover, your Wiki remarks about Qt Creator really distort its
tremendous usefulness. Of course, I don't know what you expect your
readers to do with the installed Qt building environment. But I can
assure you that in regular coding work (as I or Chris are involved
with), Qt Creator offers tremendous conveniences! The editor of Qt
Creator is great and has such features like switching between header and
source files with a click, storing a list of files that are being worked
on, locating  errors/warnings with a click in the code, finding the
definitions of classes and methods with a click, activating a debugger  etc.
And it works the same on ALL platforms, performing practically all
required configuration automatically or at worst with a couple of clicks!
PS: Just read your problems with Comodo Internet Security. This is a
familiar effect with most antivirus suites offering /dynamic/ features
(SONAR scans!). I had the same with many newly generated executables in
Norton's IS 2011. This is nothing to worry about, since the freshly
generated executables are usually unknown to the antivirus software,
hence =>  quarantine.  Just go to the config of your virus software and
enter the respective file names or subdir  in the exceptions dialog.
Here is one of many links that complaint about false alarm

This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
Celestia-developers mailing list
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
Celestia-developers mailing list

This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
Celestia-developers mailing list