[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] MSVC 8
- From: Matthew Leverton <meffer@xxxxxxxxxx>
- Date: Mon, 7 Nov 2005 21:19:59 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PVM+F9ShDvuDQ+EWZDImVAf1KPo9R2mhBsHxCpJQp9meXLT6+YNoNKX7EVFCBoLCYMij9MHP2NEOxuaj92Z7bmJPmxk1QwvEA/3rZWTxBhavXMi7Kzw+Vt5BjgDSzbq+32I0Gn0ukmVfo8vpbg7+xCdq8vC2tWyhHH0Sw0QUj4g=
> > Just demonstrating my ignorance - what is a .manifest file?
>
> It's some form of metadata for executable files. It is often used e.g.
> for enabling theming for applications.
>
It would be great if the Allegro makefile could somehow disable them.
(Maybe embedding them into the exe? I know you can do this from within
the IDE.) As it is now, millions of little .manifest files are created
and left to rot even after a make clean.
It's not a huge issue, as I think most people will use the binary
version, but it could be added to the todo list for a MSVC person to
look at.
--
Matthew Leverton