Skip to content

Commit 8930770

Browse files
committed
Merge pull request SolidCode#9 from donbright/master
clarify that there are no wildcards in OpenSCAD use/include statements
2 parents 662f853 + c90db2a commit 8930770

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

README.markdown

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,15 @@ See http://creativecommons.org/licenses/LGPL/2.1/ or the included file, lgpl-2.1
1010

1111
## Usage ##
1212

13-
You can import these files in your scripts with `use <MCAD/*.scad>`, but some
14-
files include useful constants which will be available with `include <MCAD/*.scad>`,
15-
which should be safe to use on all included files (ie. no top level code should
16-
create geometry). (There is a bug/feature that prevents including constants from
17-
files that "include" other files - see the openscad mailing list archives for more
18-
details. Since the maintainers aren't very responsive, may have to work around this
19-
somehow)
13+
You can import these files in your scripts with `use <MCAD/filename.scad>`,
14+
where 'filename' is one of the files listed below like 'motors' or
15+
'servos'. Some files include useful constants which will be available
16+
with `include <MCAD/filename.scad>`, which should be safe to use on all
17+
included files (ie. no top level code should create geometry). (There is
18+
a bug/feature that prevents including constants from files that
19+
"include" other files - see the openscad mailing list archives for more
20+
details. Since the maintainers aren't very responsive, may have to work
21+
around this somehow)
2022

2123
If you host your project in git, you can do `git submodule add URL PATH` in your
2224
repo to import this library as a git submodule for easy usage. Then you need to do

0 commit comments

Comments
 (0)