| Re: [AD] build process overhaul |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] build process overhaul
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Wed, 28 Dec 2005 15:28:51 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=jlNdnl942sbzME7bvAeBAuKcY3XkMRyDfuIqh+MrJMF9hOkAMvk27LkGzOtrob3oNxo1aRhhcRVez1f4JKjxjMczZJ4DsQOuZX5q+O2AlqUFBxUhahDmXcVHKrce5c9jEIC9DJwAW+jcehCCUrPWlZGeAej4k04sHJskM4yqhO0=
On Tuesday 27 December 2005 15:47, Peter Wang wrote:
> One reason could be line endings. If you have one Allegro working
> directory shared between Windows and Linux then a plugins.h generated
> under Windows could have line endings that gcc on Linux doesn't like.
I've never seen GCC or MSVC have problems with different line endings. I can
use GCC in Linux using DOS-style line endings and it compiles without
problems, and I can use GCC in Windows using Unix-style line endings without
problems. AFAIK, MSVC doesn't have any problems using Unix-style line endings
either.