[Gtkradiant] First time running 1.6, takes over a minute/fails to start up.

[Nerius Landys]

So how would we test the first option?

The first thing we'd need to do is find out ALL the DDLs that are
loaded by radiant.  The VC++ project file lists some of those DLLs,
but other DLLs are probably loaded by the DLLs listed.  Would we add
all DLLs loaded to the /DELAYLOAD list?

There are 3 types of things build by the VC++ project files (there are
38 total mini projects):

1. Executable (projects "radiant" and "q3map2".
2. Static libraries needed for executables and modules.
3. Modules, i.e. DDLs.

Would we add the /DELAYLOAD option to all 3 types of projects, to all
38 of the mini projects, or is it enough to add them to the top-most
"radiant" project?

Again, it's kind of a black box we're dealing with here.

On Sat, Mar 5, 2011 at 3:12 AM, Ben Noordhuis <info at bnoordhuis.nl> wrote:
> Okay, no immediate culprits but this might be first-time linking at work.
>
> Try linking DLLs with /DELAYLOAD[1] or don't link at compile time but
> LoadLibary() everything in your app. That second option might not be
> trivial to set up though.
>
> [1] http://msdn.microsoft.com/en-us/library/yx9zd12s.aspx
>
> _______________________________________________
> Gtkradiant mailing list
> Gtkradiant at zerowing.idsoftware.com
> http://zerowing.idsoftware.com/cgi-bin/mailman/listinfo/gtkradiant
>