Changes between Version 23 and Version 24 of DeveloperGuidlines


Ignore:
Timestamp:
Feb 5, 2010, 11:10:42 AM (12 years ago)
Author:
Patrick Vacek
Comment:

comma grammar

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidlines

    v23 v24  
    9595At this point you should have checked out the entire !CrypTool repository. Then compiling is pretty easy, you just go to the directory ''trunk/'' and open the '''!CrypTool 2.0.sln''' Visual Studio solution. Now Visual Studio should open with all working plugins and all components nicely arranged. In case you started Visual Studio now for the very first time, you must choose a certain settings - just select either "most common" or "C#" - you can change this at any time later. In the right hand you get the project explorer, where you see all the subprojects included in the solution. You have to look for the project '''!CryWin.exe''' there. When you found it, you need to right-click it and select '''"Set as startup-project"''' from the context menu. After you have done this, just go to the menu ''Build'' and select ''Build solution'' (clearly you can also use the hotkeys if you memorized them). Then go to ''Debug'' and click ''Start debugging'' - now !CrypTool 2.0 should start for the first time with your own compiled code - clearly you did not change yet anything, however, you have now an own build of all components (with the exception of !CrypWin and !AnotherEditor, since they are avaialable only as binary). In case it does not compile or start, please consult our [wiki:FAQ F.A.Q.] and let us know if you found a bug.
    9696
    97 As a core-developer, hence somebody who can also compile !CryWin and !AnotherEditor, you should use the '''!CrypTool 2.0.sln''' solution from the trunk\!CoreDeveloper\ directory (this directory is '''not''' visible to you if you are not a core developer). As a core developer you should know, that when compiling you '''change''' the !CryWin.exe which is visible to everybody else. Hence, when doing a checkin, please make sure you ''really'' want to checkin a new binary. As core developer you can also [BuildSetup build a new setup] and publish it as beta release on the website.
     97As a core-developer, hence somebody who can also compile !CryWin and !AnotherEditor, you should use the '''!CrypTool 2.0.sln''' solution from the trunk\!CoreDeveloper\ directory (this directory is '''not''' visible to you if you are not a core developer). As a core developer, you should know that when compiling you '''change''' the !CryWin.exe which is visible to everybody else. Hence, when doing a checkin, please make sure you ''really'' want to checkin a new binary. As core developer you can also [BuildSetup build a new setup] and publish it as beta release on the website.