Skip to content
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.

Mono-Addins 1.3.5 make install rule is failing #73

Closed
bmgandre opened this issue Jun 5, 2017 · 7 comments
Closed

Mono-Addins 1.3.5 make install rule is failing #73

bmgandre opened this issue Jun 5, 2017 · 7 comments

Comments

@bmgandre
Copy link

bmgandre commented Jun 5, 2017

Version 1.3.5 is building correctly but failing to install:

root@darkstar:/tmp/slackbuilds/mono-addins/mono-addins-c636f258d0a724e7c0de447ea717d18cb90bfb17# make DESTDIR=/tmp/package-mono-addins install
Making install in Mono.Addins
make[1]: Entering directory '/tmp/slackbuilds/mono-addins/mono-addins-c636f258d0a724e7c0de447ea717d18cb90bfb17/Mono.Addins'
make[2]: Entering directory '/tmp/slackbuilds/mono-addins/mono-addins-c636f258d0a724e7c0de447ea717d18cb90bfb17/Mono.Addins'
/usr/bin/gacutil /i ../bin/Mono.Addins.dll /f /package mono-addins /root /tmp/package-mono-addins/usr/local/lib || exit 1;
Failure adding assembly ../bin/Mono.Addins.dll to the cache: Strong name cannot be verified for delay-signed assembly
Makefile:552: recipe for target 'gac-install' failed
make[2]: *** [gac-install] Error 1
make[2]: Leaving directory '/tmp/slackbuilds/mono-addins/mono-addins-c636f258d0a724e7c0de447ea717d18cb90bfb17/Mono.Addins'
Makefile:429: recipe for target 'install-am' failed
make[1]: *** [install-am] Error 2
make[1]: Leaving directory '/tmp/slackbuilds/mono-addins/mono-addins-c636f258d0a724e7c0de447ea717d18cb90bfb17/Mono.Addins'
Makefile:350: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1

Note that DESTDIR is used for linux packing.

@malahx
Copy link

malahx commented Jun 22, 2017

Hello, I experienced the same issue on Arch Linux (and this issue seems to be duplicated with #70 ).

Nothing new? I saw that makefile/configure/autogen.sh have been deleted on the last release, is there an other way to compile this?

Thanks.

@mhutch
Copy link
Member

mhutch commented Jun 22, 2017

Installing to the GAC is no longer supported. It's intended that apps should bundle their own copy of Mono.Addins that they obtain from NuGet: https://www.nuget.org/packages/Mono.Addins

To build the NuGet packages, use msbuild /t:Release and they will be placed in the bin directory. You can set this directory as a NuGet package source, if you'd like to use binaries that yo've built from source yourself.

@anthraxx
Copy link

anthraxx commented Nov 7, 2017

@mhutch which really isn't a nice way for distributions. We aim to build things from source ourselves and not pull in precompiled binary dependencies from the internet. I'm sure there are a lot of people quite sad about this move as it creates lot of unnecessary hassle doing source builds

@Russtopia
Copy link

@mhutch @anthraxx Bleah. I was curious to try out 'Pinta', a graphics editor, on my Funtoo Linux box, but this binary dependency made me think twice. Guess I'll use something not Mono/C#-based. <shrug>

@mhutch
Copy link
Member

mhutch commented May 15, 2018

It's not that difficult to build from source.

Check out this repo, and run MSBuild /p:Configuration=Release, and it will build nupkg packages and place then in the bin subdirectory.

In the project from which you want to use this, add a nuget.config file to add the newly built packages as a package source.

<configuration>
<packageSources>
<add key="Mono.Addins Source Build" value="/path/to/mono-addins/bin" />
</packageSources>
</configuration>

@Russtopia
Copy link

Well, I guess I'll give it a second chance then :). Thank you for the tip.

@kyrios123
Copy link

Also the README still provides instruction for building with the autotools.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants