Suppose you make a copy of the "template-directories" and name the copy "my-test". Copy it with all the files and directories that are in it. The "template-directories" is what you copy when you want to write your own source. (There is a way to do this kind of script-replacement automatically. Then click on the "Save" button of the built-in editor. Delete the script in the built-in editor and copy-and-paste the contents of "projects/example-1/bin/example-1.o" into the built-in editor. Make a box, create a "New Script" in the box and open the "New Script". Now you can log into sl with your sl client. The file is needed to automatically replace scripts with the script editor built into your sl client, which will be described later. A file is generated in the "make" directory. They are needed by the build system to figure out when a script needs to be rebuilt and whether entries need to be added to a look-up table or not. Some files are generated in the "dep" directory. When you modify the source ("projects/example-1/src/example-1.lsl") just run make again after saving it, and new versions of the script will be created that replace the old ones. A debugging version is "projects/example-1/dbg/example-1.i". You will find the LSL script as "projects/example-1/bin/example-1.o". Generating dependencies: dep/example-1.di Inside the "projects" directory, you have more directories like this: You can put the "projects" directory anywhere you like, and you can give it a different name if you want to. Inside this directory, you have another one called "projects". Once cloned, you have a directory called "lsl-repo". You can run 'git clone git:///lsl-repo.git' to get it. If you want to do so, pull the repository. It´s probably more fun to be able to try out things yourself while reading this article. Please use the "discussion" page of this article to post contributions or to suggest changes so they can be added to the article. Unfortunately, this means that your modifications may be lost when I update the article and don´t see them. That´s simply the easiest and most efficient way for me. When I update the article on the wiki, I edit the whole article, delete everything and paste the new version in. This article is written in my favourite editor. You may find different software that does the same or similar things and may work better for you or not. You know better how to install software on your computer than I do, and how you install software also depends on which operating system you are using.ĭocumentation is plentiful. This article does not attempt to tell you how to install these. The repository does not contain basic standard tools like perl, cpp, make or an editor. You will have your own build system for LSL scripts when you have pulled this repository. They are organised in a directory structure which they are designed to work with. The repository contains some example sources used with this article, a few perl scripts and a Makefile. It is recommended that you pull (download) the repository. This article is accompanied by a repository. It has made it so much easier to create LSL scripts that I have made many I otherwise would never have made. The idea of using cpp for LSL scripts is also awesome. I want to thank the developers of these stargates. The idea of using cpp comes from the source of the Open Stargate Network stargates. Among the tools mentioned in this article, cpp is the tool which can make the biggest difference to how you write your sources and to how they look. One of these tools is a preprocessor called cpp. It tries to explain how to combine and how to use them for this very purpose. This article is about tools you can use to make creating LSL scripts easier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |