summaryrefslogtreecommitdiff
path: root/src/bindings/mono/efl_sharp.csproj.in
diff options
context:
space:
mode:
authorLauro Moura <lauromoura@expertisesolutions.com.br>2019-11-05 17:59:01 -0300
committerLauro Moura <lauromoura@expertisesolutions.com.br>2019-11-06 11:20:19 -0300
commit17a81bee4a53891e44a165a14ca20027f9aa0824 (patch)
tree744dcdbea803e8eaaac8af6a55c35b2d7fcaab7c /src/bindings/mono/efl_sharp.csproj.in
parent8a5976666b1566f0025f9aff394002b766069beb (diff)
csharp: Revamp dotnet support
Summary: Instead of building with a patched meson version, make use of custom targets and generated csproj files so we can used upstream meson normally. This avoids digging into "non official" dotnet stuff like calling the CSC.dll directly that the patched meson tried to do. To enable, run meson with `-Ddotnet=true`. Regarding source file dependencies, Meson has a limitation[1] about generated artifacts being placed in subdirectories. In order to correctly track these generated artifacts for dotnet, we generated them in the same folder as the csproj file through `dotnet build -o`. Instead of installing the dll like we do for mono, a nupkg is generated and installed in the same folder as the dll would be (<prefix>/lib/x86_64-linux-gnu/efl-mono-1) To avoid messing around with Nupkg caches, we reference the source project for the library directly instead of the nupkg when building the test suite. [1] https://github.com/mesonbuild/meson/issues/2320 Fixes T8168 Reviewers: bu5hm4n, woohyun, Jaehyun_Cho Reviewed By: Jaehyun_Cho Subscribers: cedric, brunobelo, felipealmeida, segfaultxavi Tags: #efl, #do_not_merge Maniphest Tasks: T8168 Differential Revision: https://phab.enlightenment.org/D9717
Diffstat (limited to 'src/bindings/mono/efl_sharp.csproj.in')
-rw-r--r--src/bindings/mono/efl_sharp.csproj.in39
1 files changed, 39 insertions, 0 deletions
diff --git a/src/bindings/mono/efl_sharp.csproj.in b/src/bindings/mono/efl_sharp.csproj.in
new file mode 100644
index 0000000000..d44aa5a8e5
--- /dev/null
+++ b/src/bindings/mono/efl_sharp.csproj.in
@@ -0,0 +1,39 @@
1<Project Sdk="Microsoft.NET.Sdk">
2
3 <PropertyGroup>
4 <OutputType>Library</OutputType>
5 <TargetFramework>netstandard@NETSTANDARD_VERSION@</TargetFramework>
6 </PropertyGroup>
7
8 <PropertyGroup>
9 <PackageId>Efl.Csharp</PackageId>
10 <Version>@EFL_VERSION@</Version>
11 <Authors>EFL Team</Authors>
12 <PackageLicenseExpression>Apache-2.0</PackageLicenseExpression>
13 </PropertyGroup>
14
15 <!-- <PropertyGroup Condition="'$(BuildType)'=='Beta'"> -->
16 <!-- <DefineConstants>EFL_BETA</DefineConstants> -->
17 <!-- </PropertyGroup> -->
18 <PropertyGroup>
19 <DefineConstants>@EFL_BETA@</DefineConstants>
20 </PropertyGroup>
21
22 <ItemGroup>
23 <Compile Include="@BINDING_SRC@/efl_mono/*.cs" />
24 <!-- FIXME Windows support -->
25 <Compile Include="@BINDING_SRC@/eo_mono/*.cs" Exclude="@BINDING_SRC@/eo_mono/*Windows.cs" />
26 <Compile Include="@BINDING_SRC@/eina_mono/*.cs" />
27 <Compile Include="@BINDING_SRC@/eolian_mono/*.cs" />
28 <Compile Include="@BINDING_SRC@/eldbus_mono/*.cs" />
29 </ItemGroup>
30
31 <!-- Calling `dotnet build` from a different folder seems to mess up the automatic source file discovery.
32 But we want them to be included only when building the lib itself.
33 -->
34 <ItemGroup Condition="'$(BuildingLib)'=='Yes'">
35 <Compile Include="./efl_mono/*.cs" />
36 <Compile Include="./*.cs" />
37 </ItemGroup>
38
39</Project>