OpenChronos Compiliation
Ok, it would appear that while the previous fix helped the entire process along a little, I still could not get OpenChronos to build.
And now I’ve run out of time, as I need to get back to music!
Ok, it would appear that while the previous fix helped the entire process along a little, I still could not get OpenChronos to build.
And now I’ve run out of time, as I need to get back to music!
Following the very useful instructions here: http://rubenlaguna.com/wp/2011/02/11/compiling-openchronos-in-windows/index.html/ I ran into a problem:
Resolving ftp.uni-kl.de (ftp.uni-kl.de)… 131.246.123.4, 2001:638:208:ef1b:0:ff:fe00:4
Connecting to ftp.uni-kl.de (ftp.uni-kl.de)|131.246.123.4|:80… connected.
HTTP request sent, awaiting response… 404 Not Found
2012-10-02 13:01:19 ERROR 404: Not Found.
I resolved it by modifying the buildgcc.pl file in the /tmp/mspgcc4-20110130 folder, changing line 136 from:
$BINUTILS_VERSION = “2.21”;
to
$BINUTILS_VERSION = “2.21.1”;
I’m not sure if it will break further into the process, I’ll update if so (and if not!)
I was running into some problems when trying to use the Crystal Report Viewer in Visual Studio 2010 to view data stored in a local DataSet. After some initial problems with the Database login prompt appearing (you need to set the source with SetDataSource on the report document object, folks), I thought i’d sorted it, until I ran into this:
Could not load file or assembly ‘file:///C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet1\crdb_adoplus.dll’ or one of its dependencies. The system cannot find the file specified.
Changing a setting in the app.config file sorted it out. Here’s what I needed to change:
<startup>
<supportedRuntime version=”v4.0″ sku=”.NETFramework,Version=v4.0″/>
</startup>
to:
<startup useLegacyV2RuntimeActivationPolicy=”true”>
<supportedRuntime version=”v4.0″ sku=”.NETFramework,Version=v4.0″/>
</startup>
Here’s the MSDN Article that explains the useLegacyV2RuntimeActivationPolicy attribute in more detail:
http://msdn.microsoft.com/en-us/library/bbx34a2h(v=vs.100).aspx
Whether this causes me headaches further down the development path remains to be seen……