/[projet1]/public/pc/tools/osdk/main/Osdk/_final_/documentation/doc_creating_project.htm
Defence Force logotype

Contents of /public/pc/tools/osdk/main/Osdk/_final_/documentation/doc_creating_project.htm

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1002 - (show annotations)
Sun Dec 8 10:50:26 2013 UTC (5 years, 11 months ago) by dbug
File MIME type: text/html
File size: 4536 byte(s)
Resynchronized my own changes to the OSDK with what was in the depot.
From now on I will continue the changes directly with the depot version, and try to update more regularly.
The reason I had this big change is that I had two computers with local changes done in demo parties when working on demos, where I did the fixes to handle Euphoric and Oricutron, plus new tools, modified tools, etc... giant mess.
I do not guarantee that what is on the depot is bug free, but it's the version I'm using right now (My OSDK var points to the public\pc\tools\osdk\main\Osdk\_final_ folder.
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
2
3 <HTML lang=fr dir=ltr>
4 <HEAD>
5 <meta name="robots" content="noindex">
6 <meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
7 <title>OSDK - Creating project</title>
8 <link href="documentation.css" rel="stylesheet" type="text/css">
9 </HEAD>
10
11 <BODY>
12
13 <hr>
14 <A href="documentation.htm"><img src="arrow_back.gif"></A>
15 <img src="pics/osdk_logo_small.png">
16 <hr>
17
18 <h1>Creating project</h1>
19
20
21
22 <p id=chapter>How to use it for new projects</p>
23
24 <p>The only thing you have to do, is to create a folder, put your source codes, and copy from the sample directory the three batch files:
25 </p>
26 <pre>
27 osdk_build.bat
28 osdk_execute.bat
29 osdk_showmap.bat
30 osdk_config.bat
31 </pre>
32
33 <p>We are interested by the last one. Just edit this file, and look at those lines:
34 </p>
35 <pre>
36 SET OSDKADDR=$600
37 SET OSDKNAME=demo
38 SET OSDKFILE=main display sound packer
39 SET OSDKLINK=
40 SET OSDKCOMP=
41 </pre>
42
43 <p>those parameters define how the program will be constructed:
44 </p>
45 <ul>
46 <li>the <b>OSDKADDR</b> variable contains the link adress. The default value is $600
47 </li>
48 <li>the <b>OSDKNAME</b> variable contains the name of the TAP file to generate. The default value is OSDK.
49 </li>
50 <li>the <b>OSDKFILE</b> variable contains the list of all files to build. In the example above, the DEMO.TAP program will be made from MAIN.C DISPLAY.S SOUND.S and PACKER.C. As you can see, the extensions are not given. It means that you cannot have two files having the same name but with a different extension.
51 </li>
52 <li>the <b>OSDKLINK</b> variable contains the list of parameters the linker will receive. The value <b>-B</b> will tell the linker to not automaticaly
53 happend 'header.s' and 'tail.s' thus giving you full control on how your program will fit in memory. Good for pure assembly code programs.
54 </li>
55 <li>the <b>OSDKCOMP</b> variable contains the list of parameters the compiler will receive.
56 If you don't fill it, it will be initialized by default to the options -O2.
57 You can try -O3 if you wish more aggresive optimizations (beta test, could produce wrong code)
58 </li>
59 </ul>
60
61 <p>The OSDK also support some other variables, here they are for exaustivity:
62 </p>
63
64 <ul>
65 <li>the <b>OSDKDOSBOX</b> variable contains the location of DOSBOX if it is installed. You need that only if you are trying to use Euphoric on a recent machine.
66 </li>
67 <li>the <b>OSDKTAPNAME</b> variable contains the name of the loaded program inside the TAP file (the one that appears in the Oric status bar). The default value is OSDK.
68 </li>
69 <li>the <b>OSDKBRIEF</b> variable if empty automatically insert pauses on the build process and show verbosity messages (default), else it will quit without pausing and show less verbosity.
70 </li>
71 <li>the <b>OSDKHEAD</b> variable content is passed to HEADER.EXE. The value <b>-S1</b> will tell it to show the size of the final executable (practical when writing 256 bytes intros).
72 </li>
73 </ul>
74
75
76 <p>And internally during the Build time the OSDK defines some other variables from the existing ones:
77 </p>
78
79 <ul>
80 <li>the <b>OSDKB</b> variable contains the location of the executable folder (%OSDK%\BIN)
81 </li>
82 <li>the <b>OSDKT</b> variable contains the location of the tempory folder (%OSDK%\TMP)
83 </li>
84 </ul>
85
86
87
88 <p>The only thing you have to made, is edit this file to make it reflect your needs.
89 </p>
90
91 <p><i>See also:</i>
92 <ul>
93 <li><A href="doc_linker.htm">Linker</A></li>
94 </ul>
95 </p>
96
97
98 <p id=chapter>For Visual Studios Users</p>
99
100 <p>If like me, you are used to use a modern IDE like Visual Studios, you can configure it in order to be able to edit, compile, and test directly from the VC IDE !
101 In order to do that, you have to create a NEW PROJECT, and choose MAKEFILE.
102 In the menu "PROJECT/SETTING", choose "GENERAL" and enter the following line into the "Build command line" box:
103 </p>
104
105 <pre>
106 %OSDK%\Bin\vc_make.bat
107 </pre>
108
109 <p>this way, you will be able to compile using the "F7" key, the error messages appear into the output window of visual studios. Clean, isn't it ?
110 </p>
111
112 <p>If you wish to be able to debug the code, you can also launch Euphoric from visual studios. Instead of "GENERAL" go to "DEBUG", and in the "Executable for debug session" box, simply enter the following line:
113 </p>
114
115 <pre>
116 OSDK_EXECUTE.BAT
117 </pre>
118
119
120
121 <hr>
122 <A href="documentation.htm"><img src="arrow_back.gif"></A>
123 <img src="pics/osdk_logo_small.png">
124 <hr>
125
126 </BODY>
127 </HTML>
128
129

  ViewVC Help
Powered by ViewVC 1.1.26