[Mono-dev] csproj files for Mono's class libraries.
monoman at gmail.com
Mon Feb 14 08:59:24 EST 2011
This stackoverflow question/answer is also interesting in considering
moving the build to xbuild:
Rafael "Monoman" Teixeira
"We live in a world operated by science and technology. We have also
arranged things so that almost no one understands science and
technology. This is a prescription for disaster. We might get away
with it for a while, but sooner or later this combustible mixture of
ignorance and power is going to blow up in our faces."
On Mon, Feb 14, 2011 at 11:28 AM, Rafael Teixeira <monoman at gmail.com> wrote:
> Sorry, my memory failed me. VS2010 doesn't support multi-targetting in
> the same csproj, also it doesn't honor things like
> <Compile Include="Core\Common.cs"
> Condition="'$(TargetFrameworkVersion)' == '2'" />
> So you need to keep separate .csproj for each targetted framework. It
> seems that there are different .sources files too (as for the
> droid/iphone versions of System.Data).
> I'll try to cook such a task.
> Rafael "Monoman" Teixeira
> "We live in a world operated by science and technology. We have also
> arranged things so that almost no one understands science and
> technology. This is a prescription for disaster. We might get away
> with it for a while, but sooner or later this combustible mixture of
> ignorance and power is going to blow up in our faces."
> -Carl Sagan
> On Mon, Feb 14, 2011 at 11:20 AM, Marek Safar <marek.safar at gmail.com> wrote:
>>>> You can have the csproj reference the .sources file externally, and use a
>>>> small Task to transform the list of files into Compile elements. This works
>>>> in VS for building, but does not show the sources as files in the csproj via
>>>> the UI. So, depending what you want...
>> Something like this
>> our xbuild master can probably give better guidance.
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list