letiemble
commented
11 years ago The issue seems to be linked to parallel installation of the pkg-config binaries.
- The Mono framework contains a pkg-config binary. Until recently (I would say Mono 2.8), a symbolic link was created to this binary from /usr/bin/pkg-config. It is not the case anymore.
- Until the 5.0.2090, the Monobjc's installer was (re)creating this symbolic link tfor both NAnt and MSBuild tasks. But it appeared that this operation have broken many existing setups. This is why the symbolic link creation has been removed.
In order to check if your system is ok, open a Terminal:
- execute "which pkg-config", to see if pkg-config is found on the path
- if not, create a symlink to the "pkg-config" binary: "sudo ln -s /Library/Frameworks/Mono.framework/Commands/pkg-config /usr/bin/pkg-config"
- re-execute "which pkg-config", to see if pkg-config is found on the path
After that, the tasks should run ok.
lemonmojo
Sorry to bother you again...
Just updated Mono to 2.10.12 and the MSBuild Tasks seem to be broken again. This time, the CoreBundleNative Target fails with the following exception:
/Library/Frameworks/Mono.framework/Versions/2.10.12/lib/mono/4.0/Monobjc.CocoaApplication.targets: error : System.ComponentModel.Win32Exception: ApplicationName='pkg-config', CommandLine='--cflags mono-2', CurrentDirectory='' at System.Diagnostics.Process.Start_noshell (System.Diagnostics.ProcessStartInfo startInfo, System.Diagnostics.Process process) [0x00000] in:0
at System.Diagnostics.Process.Start_common (System.Diagnostics.ProcessStartInfo startInfo, System.Diagnostics.Process process) [0x00000] in :0
at System.Diagnostics.Process.Start () [0x00000] in :0
at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:Start ()
at Monobjc.Tools.Utilities.ProcessHelper.Execute () [0x00000] in :0