Re: Tree structure for a win32 application deployment



jcupitt gmail com:

You can remove all of the gtk .exes, you just need to leave the .dlls
behind. The only one you might need to leave is the spawn helper (I
think). If you're not spawning child processes with glib then you can
remove this one too.

That's beyond the point.
I'm happy with the gtk toolkit I have, I wrote .exes, but I meant all the files that sould to be in the gtk bin directory.



In any case, why does this matter? Your users will (I guess) be
clicking a shortcut icon to launch your app, they won't know or care
what other programs are in the same directory.

They don't, but I do.
If I want to refer to some non-gtk file in my app I need to know where this file is, For example a ini file, having my_app.exe in the bin directory forces me to put the ini file in that directory too or to write code to point to it using ../my_app.ini and I don't like it.
--
Regards,
Manuel Ferrero
R&D department

Reer SpA	
Tel.  +39 011 2482215
Fax. +39 011 859867

L'utilizzo non autorizzato del presente messaggio e' vietato e potrebbe costituire reato.
Se il presente messaggio non e' a Lei indirizzato, il suo contenuto non deve essere considerato
come trasmesso o autorizzato dalla Reer SpA; in tale caso Le saremmo grati se, via e-mail,
ce ne comunicasse l'errata ricezione.

The unauthorized use of this e-mail is prohibited and could constitute an offence.
If you are not the intended recipient of this message its contents shall be understood as neither
given nor endorsed by Reer SpA. Please notify Reer SpA by e-mail immediately in that case.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]