You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refine the DevREADME.md for more cleaner setup and compile steps (#65)
##### Objective
I want to make the devREADME.md has more cleaner steps for new developers.
##### Abstractions
Now for new developer it should only do two things:
1. git pull to get the codes
2. run` python pack.py` to compile the codes
Other details information like `npm install` or copy the correct file to correct location is hidden in the pack.py file.
And I also added one section how to setup the environment in Autodesk domain to work around the NPM local setting limitation.
##### Tests performed
##### Screen shot
No applicable for this PR.
Copy file name to clipboardExpand all lines: DevREADME.md
+12-29Lines changed: 12 additions & 29 deletions
Original file line number
Diff line number
Diff line change
@@ -2,27 +2,17 @@
2
2
3
3
AutoCAD Lisp Extension is a vscode extension for debug AutoCAD AutoLISP. The Extension plays the roles of both debug adapter and language server which could enable you debug lisp with AutoCAD. The following description is for developers.
4
4
5
-
## How to setup the Dev Env
6
-
npm install -g yarn (if it's not installed yet)
5
+
## How to setup the Dev env and compile the code
7
6
8
-
Then you could setup the develop environment by:
7
+
You could do all the steps in the script pack.py, it is python2; or run it directly:
9
8
```
10
9
cd AutoLispExt
11
-
npm install --global gulp-cli
12
-
npm install
13
-
```
14
-
__NOTE:__ You may see a warning `"The engine "vscode" appears to be invalid"` while running `yarn install`. This is a known problem. Please refer to the [VSCode issue](https://github.com/microsoft/vscode/issues/91009).
If you only want to build the ts file and debug it via F5, you can run:
12
+
### How to compile the codes
13
+
The script pack.py will copy some utility files to correct location for making package. After run that script and then change some TS codes, you can also use the follow command to compile codes simply:
23
14
```
24
-
=> Windows: winCompile.bat
25
-
=> Otherwise: ./macCompile.sh
15
+
npm run compile
26
16
```
27
17
28
18
## How to debug the extension
@@ -32,36 +22,29 @@ If you only want to build the ts file and debug it via F5, you can run:
32
22
3. hit F5 and select "Extension Client", then it will start another vscode instance with running the extension.
33
23
4. Do some operations to invoke the codes which are added breakpoints, vscode will stop in the first instance.
34
24
35
-
36
25
## How to package the extension
37
26
38
27
You could package the extension by:
39
28
```
40
-
cd AutoLispExt
41
-
gulp package
42
-
```
43
-
Note that don't run "publish" command otherwise you make sure you want to do.
44
-
For the publish command it will release current version extension to vscode market.
45
-
46
-
## The Script pack.py
47
-
48
-
You could do all above steps by the script pack.py, it is python2
49
-
```
50
-
cd AutoLispExt
51
29
python pack.py
52
30
```
31
+
It will create the package in the current folder.
53
32
54
33
## Run tests
55
34
56
35
You have two ways to run the tests:
57
36
- Run inside the VS Code and begin debugging by choosing "Extension Tests"
58
37
- Run on terminal outside of VS Code and make sure no VS code is running (VS Code terminal will not work due to VS Code limitation)
59
38
```
60
-
yarn test
39
+
npm run test
61
40
```
62
41
63
42
### The following steps require access to Autodesk network resources and therefore can only be done by Autodesk employees
64
43
44
+
## NPM settings
45
+
Because the mandatory local NPM setting in Autodesk, for Autodesk developer you can simply replace all the ocurrences in pacake-lock.json like:
46
+
replace https://registry.npmjs.org/ with https://art-bobcat.autodesk.com:443/artifactory/api/npm/autodesk-npm-virtual/
0 commit comments