Post by fenfen on Aug 6, 2015 20:32:19 GMT -8
www.dropbox.com/s/o9k66hwi4dss3uf/Radegast-2.19.1466.0R-installer.exe?dl=0
okay so i sucessfully compiled the newest 2.19.1466 for windows using Sharpdevelop 4.4. this target framework & platform is stock, but with release flag instead of stock debug. runs great. I already had nisi to compile the installer so here you go Radegast Fans! Just click the small print to continue to download if dropbox sign up pops up...
Do not link back to my drop box form any other site!
The windows tutorial to compile is LACKING so:
1: Go to github, search for radegast. Download ZIP of radegast master or 2.19 whatever version, then dl openverslib by clicking the numbers after the darkened folder for it at github on the radegast dl page you where just at. (dark folders are dependency)
Unzip it all into folders, then copy paste the contents of openverslib124... folder to the openverslib folder.(should be lots of files not one folder)
2: Run runprebuild2010.bat in both radegast & openverslib, if you are on win XP like me cause you can't use higher. Don't bother with compile.bat most likely you dont have all the garblygouk set up to do that.
3A: OPEN either VS2010 pro or Sharpdevlop or your fav C# compiler. I'm using Sharpdevlop.
You get error "The OutputPath property is not set for project 'OpenMetaverse.csproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Debug' Platform='x86'. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform."
radegast or anything else that references it's code needs to know where it is!
3B: IN SharpDevelop:Expand "Solution Radegast", the right click "Radegast" sub-project, click properties. now a properties mini window will open. It might be squashed to a side depending on your lay out, just drag the others around.
Now Click "Reference Paths" tab. you see that the eventual out put path is already set, and it knows where it self is at already okay???
SO! click the "tripple dots" find openverslib folder, then hit "add path", then update,at the top menu save icon. DONE!
3C: Now rinse and repeat do that task for all the sub-projects that have openverslib in their references, or do em all can't hurt.
Almost finished, now openverlib needs an output path so go to properties gain, for all four openverslib projects this time use the "compile" tab half way down out put path set it to "..\..\bin\" with out the "". save!
3D: IF you reopen the solution file to check for errors you get: Error loading code-completion information for fmodex-dotnet.dll from fmodex-dotnet.dll: Could not find assembly file. You can either add another refrance path to \radegast\assemblies\ OR make life easy and just copy paste the .dll/.dlls in that folder to the one with the solution file, then it finds it automatic.
4: Finally select "Solution Radegast" at the top and build menu build! you are finished winner! output is in bin folder.
If you want a slightly lighter weight version in the build menu "set configuration"->Release. then build again.
okay so i sucessfully compiled the newest 2.19.1466 for windows using Sharpdevelop 4.4. this target framework & platform is stock, but with release flag instead of stock debug. runs great. I already had nisi to compile the installer so here you go Radegast Fans! Just click the small print to continue to download if dropbox sign up pops up...
Do not link back to my drop box form any other site!
The windows tutorial to compile is LACKING so:
1: Go to github, search for radegast. Download ZIP of radegast master or 2.19 whatever version, then dl openverslib by clicking the numbers after the darkened folder for it at github on the radegast dl page you where just at. (dark folders are dependency)
Unzip it all into folders, then copy paste the contents of openverslib124... folder to the openverslib folder.(should be lots of files not one folder)
2: Run runprebuild2010.bat in both radegast & openverslib, if you are on win XP like me cause you can't use higher. Don't bother with compile.bat most likely you dont have all the garblygouk set up to do that.
3A: OPEN either VS2010 pro or Sharpdevlop or your fav C# compiler. I'm using Sharpdevlop.
You get error "The OutputPath property is not set for project 'OpenMetaverse.csproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Debug' Platform='x86'. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform."
radegast or anything else that references it's code needs to know where it is!
3B: IN SharpDevelop:Expand "Solution Radegast", the right click "Radegast" sub-project, click properties. now a properties mini window will open. It might be squashed to a side depending on your lay out, just drag the others around.
Now Click "Reference Paths" tab. you see that the eventual out put path is already set, and it knows where it self is at already okay???
SO! click the "tripple dots" find openverslib folder, then hit "add path", then update,at the top menu save icon. DONE!
3C: Now rinse and repeat do that task for all the sub-projects that have openverslib in their references, or do em all can't hurt.
Almost finished, now openverlib needs an output path so go to properties gain, for all four openverslib projects this time use the "compile" tab half way down out put path set it to "..\..\bin\" with out the "". save!
3D: IF you reopen the solution file to check for errors you get: Error loading code-completion information for fmodex-dotnet.dll from fmodex-dotnet.dll: Could not find assembly file. You can either add another refrance path to \radegast\assemblies\ OR make life easy and just copy paste the .dll/.dlls in that folder to the one with the solution file, then it finds it automatic.
4: Finally select "Solution Radegast" at the top and build menu build! you are finished winner! output is in bin folder.
If you want a slightly lighter weight version in the build menu "set configuration"->Release. then build again.
