wiki.openlighting.org - User contributions [en]

# Cavendish skin uses APIs deprecated in 1.42; keep those warnings out of the error log $wgDeprecationReleaseLimit = "1.41"; $wgEnableSidebarCache = true; $wgParserCacheType = CACHE_DB; https://wiki.openlighting.org/api.php?action=feedcontributions&feedformat=atom&user=216.239.45.4 wiki.openlighting.org - User contributions [en] 2026-11-04T01:56:29Z User contributions MediaWiki 1.43.11 https://wiki.openlighting.org/index.php?title=OLA_developer_info&diff=4039 OLA developer info 2011-12-29T18:45:25Z

<p>216.239.45.4: /* HTTP Server */</p> <hr /> <div>This attempts to describe the internal structure of OLA, in particular the classes that make up plugins. Read [[Using_OLA]] first to understand the Port/Device/Universe/Plugin terminology. <br /> <br /> == Core Classes ==<br /> <br /> === DmxBuffer ===<br /> <br /> The DmxBuffer class allows DMX data to be passed around the code, while avoiding unnecessary copying. DmxBuffer is defined in include/ola/DmxBuffer.h<br /> <br /> <pre><br /> DmxBuffer data; // new empty buffer<br /> data.Size(); // size of the buffer, 0 to 512<br /> data.Blackout(); // set all channels to 0<br /> data.Set(data, length); // set the buffer from a uint8_t*<br /> data.Get(data, &length); // copy the data buffer into the memory pointed to by data<br /> <br /> Dmxbuffer data2 = data; // no copy<br /> </pre><br /> <br /> DmxBuffers are very similar to the boost [http://www.boost.org/doc/libs/1_43_0/libs/smart_ptr/shared_ptr.htm shared_ptr]<br /> <br /> === Callbacks ===<br /> <br /> Callbacks are similar to function pointers, they allow both functions and methods to be invoked at a later time with data from either/both the time the Callback is constructed and the time the Callback is executed. The classes are defined in include/ola/Callback.h<br /> <br /> All Callbacks have a Run() method, which is how the Callback is executed.<br /> <br /> Callbacks come on two varieties, Persistent and SingleUse. SingleUse callbacks delete themselves after Run() is called so you don't have to.<br /> <br /> <pre><br /> // wrap a function that takes no args and returns a bool<br /> SingleUseCallback<bool> *callback1 = NewSingleCallback(&Function0);<br /> <br /> // some time later<br /> bool result = callback1->Run();<br /> // callback1 has deleted itself at this point<br /> <br /> // create a Callback for Method1 of the Object class and bind TEST_VALUE as the first arg<br /> Callback<void> *callback2 = NewCallback(object, &Object::Method1, TEST_VALUE);<br /> <br /> // this will call object->Method1(TEST_VALUE)<br /> callback2->Run();<br /> // this wasn't a SingleUse Callback, so callback is still around and needs to be deleted manually.<br /> delete callback2;<br /> <br /> // create a Callback for a method that takes 1 arg and returns void<br /> BaseCallback1<void, unsigned int> *callback3 = NewCallback(object, &Object::Method1);<br /> <br /> // Call object->Method1(TEST_VALUE)<br /> callback3->Run(TEST_VALUE);<br /> // callback3 is still around at this stage<br /> delete callback3;<br /> <br /> // create a callback for a method that takes 2 args and returns void<br /> BaseCallback2<void, int, int> *callback4 = NewSingleCallback(<br /> object,<br /> &Object::Method2,<br /> TEST_VALUE);<br /> <br /> // This calls object->Method2(TEST_VALUE, TEST_VALUE2);<br /> callback4->Run(TEST_VALUE2);<br /> // callback4 is still around<br /> delete callback4;<br /> </pre><br /> <br /> === SelectServer & Sockets ===<br /> <br /> The SelectServer is the dispatcher at the core of OLA and is defined in include/ola/network/SelectServer.h. It waits for events, and when an action occurs calls the specified method. The SelectServer can also be used to register Timeouts (called every N ms) and Loop functions (shouldn't be used).<br /> <br /> === Logging ===<br /> <br /> The logging macros are defined in include/ola/Logging.h. Logging outputs behave like streams:<br /> <br /> <pre><br /> OLA_FATAL << "foo";<br /> OLA_ERROR << "bar";<br /> OLA_INFO << "baz";<br /> OLA_DEBUG << "bat";<br /> </pre><br /> <br /> === TimeStamp and TimeInterval ===<br /> <br /> These are basic classes used for dealing with Time. They are defined in include/ola/Clock.h.<br /> <br /> <pre><br /> // get the current time<br /> TimeStamp timestamp, timestamp2;<br /> Clock::CurrentTime(&timestamp);<br /> <br /> // sleep for a bit<br /> usleep(10000);<br /> <br /> // print the duration we slept for<br /> Clock::CurrentTime(&timestamp2);<br /> TimeInterval interval = timestamp2 - timestamp;<br /> cout << interval << endl;<br /> </pre><br /> <br /> === String Utils ===<br /> <br /> While not a class, include/ola/StringUtils.h defines a number of helper functions for dealing with Strings.<br /> <br /> === Network Utils ===<br /> <br /> include/ola/network/NetworkUtils.h has helper methods for converting between endian formats, and converting IPv4 addresses to strings and visa-versa.<br /> <br /> <br /> == Plugin System ==<br /> <br /> We'll use plugin to refer to the entire module (Plugin, Devices & Ports), and Plugin to refer to the class that inherits from Plugin.<br /> <br /> Plugins create and register Devices, which each consist of 0 (obviously not useful) or more Ports. A Plugin generally does a bit of work when it starts to detect devices, then leaves all work to the individual Devices and Ports.<br /> <br /> [[Image:ola_plugin_uml.png]]<br /> <br /> Each plugin implements the classes in blue. Of course, you can choose not to inherit from the BasicPort / Device / Plugin classes and do everything yourself.<br /> <br /> === PluginAdaptor ===<br /> <br /> The PluginAdaptor is the interface between plugin code and the core OLA objects. Each Plugin object has a pointer to a plugin adaptor in the instance variable m_plugin_adaptor.<br /> <br /> === Plugins ===<br /> <br /> The AbstractPlugin interface is defined in include/olad/Plugin.h. The Plugin class implements most of this interface, and leaves Id(), PluginPrefix(), StartHook(), StopHook(), SetDefaultPreferences() and Description() to be implemented by the child classes.<br /> <br /> <br /> The startup sequence for a Plugin object is:<br /> * From within DynamicPluginLoader::LoadPlugins an instance of the plugin is created<br /> * If the ShouldStart() method returns False, nothing else happens, otherwise the Start() method is called.<br /> * The Start() method calls LoadPreferences() which in turn calls SetDefaultPreferences(), this last method gives the Plugin the opportunity to setup the Preferences object.<br /> * if SetDefaultPreferences() doesn't fail, StartHook() is called where new Devices are created. m_plugin_adaptor->RegisterDevice() should be called to add new Devices.<br /> <br /> <br /> During the shutdown sequence:<br /> * Stop() is called, which in turn calls StopHook()<br /> * StopHook should call m_plugin_adaptor->UnregisterDevice() for any devices registered during the start phase.<br /> * delete is then called on the Plugin object<br /> <br /> <br /> At any time a the following methods can be called:<br /> * Id()<br /> * Name()<br /> * Description()<br /> <br /> === Devices ===<br /> <br /> The interface to Devices is defined in include/olad/Device.h as AbstractDevice, again the Device class implements most of this interface, leaving the derived classes to fill in a couple of methods:<br /> * DeviceId() - returns a unique persistent string identifying this device<br /> * StartHook() - this should create the port objects for a device.<br /> <br /> <br /> === Ports ===<br /> <br /> Ports are the objects that actually read/write DmxBuffers. Defined in include/olad/Port.h there is the base interface Port, and then two child interfaces, InputPort and OutputPort. The BasicInputPort and BasicOutputPort provide partial implementations for these two interfaces.<br /> <br /> <br /> At a minimum , an OutputPort needs to provide the following methods:<br /> * WriteDMX(const DmxBuffer &buffer, uint8_t priority) <br /> * Description()<br /> <br /> <br /> And an InputPort needs to provide:<br /> * ReadDMX()<br /> * Description()<br /> <br /> <br /> A call to ReadDMX() is triggered by calling DmxChanged() on a InputPort object. This causes the universe the port is bound to to fetch the new DMX data. Both ReadDMX() and WriteDMX() must be non-blocking, blocking here will delay the main processing loop. To satisfy this, most ports use this sequence of events:<br /> <br /> * register a Socket for reading with the SelectServer<br /> // some time later<br /> * receive notification that there is new data on the socket<br /> * read the data and copy it to a buffer<br /> * call DmxChanged() to notify the bound Universe we have new data<br /> * the Universe then calls ReadDMX()<br /> <br /> <br /> Often more than one port will use the same file descriptor. This means the device is responsible for reading the data and dispatching to the right port. <br /> <br /> Here's an example of how dmx data is received from the UsbPro Device.<br /> <br /> The UsbProDevice will have been registered using plugin_adaptor->RegisterSocket(). When input becomes available the following sequence happens:<br /> device->action() // signals the device that new data is available<br /> widget->recv() // tells the widget to read more data<br /> widget->do_recv() // reads the data from the fd<br /> widget->handle_cos() // handles the change-of-state message from the widget<br /> device->new_dmx() // signal the device that new dmx data has arrived <br /> port->DmxChanged() // signal the universe that new dmx data has arrived<br /> // if this port is bound to a universe, the universe will then call<br /> port->ReadDMX()<br /> device->get_dmx()<br /> widget->get_dmx()<br /> <br /> Of course, the plugin authors are free to implement this however they like.<br /> <br /> <br /> === Config Messages ===<br /> <br /> Config messages are handled a little differently for two reasons:<br /> * The configure() method in a plugin has to return a response immediately. We don't want to block because we'll delay all lla processing. The new RPC subsystem removes this limitation.<br /> * Sending a PARAMETER_REQUEST to the widget doesn't generate a response immediately (in fact it may not generate one at all).<br /> <br /> To work around this, we send a parameter_request when we start the device, and then anytime we set parameters. In the meantime we store the parameters in the widget object and return those. The sequence looks like:<br /> <br /> device->configure()<br /> device->config_get_params()<br /> widget->get_parms()<br /> <br /> * What is the interface between the LLA core and LLA plugins?<br /> <br /> See above and the files plugin.h, device.h and port.h. The create() call will be passed a PluginAdaptor object which can then be used to register/unregister file descriptors, loop functions, timeouts and devices.<br /> <br /> * What is the interface between the LLA core and other apps/clients to LLA like QLC?<br /> <br /> All clients should use the LlaClient library. This needs better documentation.<br /> <br /> * How is functionality split between the usbpro plugin and the example program?<br /> <br /> The example program constructs configuration request messages and sends them (using LlaClient) to the Lla Core. The core routes this message to the plugin, which then returns a response message. This response is passed back to the client.<br /> <br /> == RPC Mechanism ==<br /> <br /> RPCs are at the heart of OLA. The RPC system is built on [http://code.google.com/apis/protocolbuffers/ protocol buffers]. olad/OlaServerServiceImpl.h provides the implementation for the RPCs on the server side.<br /> <br /> == HTTP Server ==<br /> <br /> The HTTP server is provided by [http://www.gnu.org/software/libmicrohttpd/ microhttpd]. The olad/HttpServer.h class provides a C++ class wrapper around the microhttpd code, and then olad/OlaHttpServer.h implements the OLA specific behavior.<br /> <br /> == Ideas for easy configuration ==<br /> For some users, it will be useful to have a "auto-connect" feature. When a attached device is discovered (either when LLA i started or when a new device is attached), the user could be asked if the available ports (input as well as output) should be patched to the lowest available universes.<br /> <br /> * Enable auto-connect ( OFF|connect whatever comes first|connect by stored patch layout)<br /> * Save a given combination of devices (just by type or with unique ID's from serial numbers, USB device ID's etc)<br /> <br /> Which devices cannot be autodetected?<br /> <br /> == About device config messages ==<br /> <br /> We need a way to tune settings on a port/device that the LLA Core doesn't know about. To enable this, the LlaClient provides a method dev_config(unsigned int dev, LlaDevConfigMsg *msg)<br /> <br /> The LlaDevConfigMsg is an interface which declares one method: pack(uint8_t buffer, unsigned int length).<br /> On the device side, we declare a method configure(uint8_t *request, int length)<br /> <br /> So to use this:<br /> <br /> On the client<br /> <br /> MyObserver::dev_config(unsigned int dev, uin8_t *res, unsigned int length) {<br /> MyLlaDevConfigMsg msg = parse_message(data, length);<br /> // do something with the result<br /> }<br /> <br /> int main() {<br /> // all the setup code<br /> <br /> MyObserver observer;<br /> // the observer gets the dev_config() callback<br /> lla_client->set_observer(&observer);<br /> <br /> MyLlaDevConfigMsg msg;<br /> // set some fields<br /> msg.foo = 1<br /> lla_client->dev_config(device_id, &msg); //calls pack() on the message<br /> }<br /> <br /> In the device:<br /> <br /> MyDevice::configure(data, length) {<br /> MyLlaDevConfigMsg msg = parse_message(data, length);<br /> // do something with the message<br /> <br /> MyLlaDevConfigMsg *response = new MyLlaDevConfigMsg();<br /> // response is deleted by the lla core<br /> return response;<br /> }<br /> <br /> <br /> == The tool app "lla-usbpro" ==<br /> <br /> The purpose is to set and get the settings that reside in the ''USB Pro'' box.<br /> <br /> The communication with ''USB Pro's'' seems to go via the LLA core, and lla-usbpro registers as a LLA client, and uses some event handlers.<br /> <br /> As defined in the device spec. (PDF from Enttec):<br /> <br /> label=3 response<br /> *1. data byte= Firmware version LSB. Valid range is 0 to 255.<br /> *2. data byte=Firmware version MSB. Valid range is 0 to 255.<br /> *3. data byte=DMX output break time in 10.67 microsecond units. range=[9-127] (96.03 - 1355.09 micro seconds)<br /> *4. data byte=DMX output Mark After Break time in 10.67 microsecond units. range=[1-127] (10.67 - 1355.09 micro seconds)<br /> *5. data byte=DMX output rate in packets per second. range=[1-40]<br /> *x. data byte= some user configuration of the requested size<br /> <br /> The serial number is is decoded (from 4 bit Binary Coded Decimal) in lla-usbpro, not the plugin.<br /> <br /> ==Unsupported USB devices==<br /> <br /> * [[Peperoni Light| Peperoni]] [[Rodin1]] (but this is supported directly by [[QLC]])<br /> * [[Peperoni Light|Peperoni]] [[USBDMX21]]<br /> * [[USB DMX]] from usbdmx.com<br /> * [[Sandsys]] [[UMX2]]<br /> * [[Sandsys]] [[UMX4]]<br /> ''Peperoni and usbdmx are probably easy to implement. The specs and source code examples are available.''</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Arduino_RGB_Mixer&diff=3926 Arduino RGB Mixer 2011-08-31T17:02:39Z

<p>216.239.45.4: /* Host Software */</p> <hr /> <div>{{Features|free=yes|linux=yes|osx=yes|rdm=yes}}<br /> [[Image:Arduino-RGB-RDM.jpg|right|200px]]<br /> [[Image:Ardunio-RGB.jpg|right|200px]]<br /> <br /> This page describes how to build a 2 LED RGB (6 channel) color mixer using an [[Arduino]] and [[OLA]] and [[QLC]]. The Arduino is programed to emulate a [[DMX USB Pro]] and implements the [[USB Protocol Extensions]] along with [[RDM]].<br /> <br /> === Features ===<br /> <br /> * Six channel PWM controller (multiple personalities enable inversion of the output)<br /> * DMX Address and Device label can be set using RDM<br /> * Identify led (useful when multiple devices are in use so you can identify which device is which)<br /> * Power cycle counter<br /> * Optional Temperature Sensor<br /> * Serial number (UID) can be set remotely<br /> <br /> === Parts ===<br /> <br /> * LED strip lights, Ikea has a set which are reasonably cheap and come with mounting brackets: [http://www.ikea.com/us/en/catalog/products/50119407 Dioder] - $50<br /> * A power supply for the led lights, make sure it can provide enough current for the amount of leds you plan to use. You can use the one from the Ikea lights.<br /> * An [[Arduino]], I used the [http://arduino.cc/en/Main/ArduinoBoardDuemilanove Duemilanove] - $30<br /> * Parts to make a driver circuit: 3 x 2N2222 transistors, 3x 2.2k resistors, small PCB - $10<br /> * A 110ohm resistor (or 100 + 10 ohm) to disable the auto-reset on the new Arduino boards.<br /> * A LM35DZ temperature sensor - $2<br /> * A LED to indicate the device is in identify mode - 50c<br /> <br /> In the example above the Ikea leds run from 12V and draw ~420mA when all colors are on so you need to make sure the driver circuit and power supply is sized correctly.<br /> <br /> ==Hardware==<br /> <br /> === LED Driver ===<br /> <br /> The LEDs use 12V while the Arduino supplies 5V so we need to make a driver circuit. The one below should be good up to 600mA per channel or so.<br /> <br /> [[Image:RGB-arduino-driver.png|center]]<br /> <br /> You need one of these per channel. The inputs should be connected to the PWM pins on the Arduino (pins 3, 5, 6, 9, 10, 11 on a Duemilanove). Make sure you connect the ground of both circuits.<br /> <br /> === Identify LED ===<br /> <br /> RDM allows a device to be put into 'identify mode'. The RGB Mixer uses an LED to indicate when identify mode is enabled. This LED should be connected between pins 12 and ground.<br /> <br /> === Temperature Sensor ===<br /> <br /> The output of the LM35 should be connected to analog pin 0 as shown on http://www.danielandrade.net/2008/07/05/temperature-sensor-arduino/<br /> <br /> ===Disable Auto-Reset===<br /> <br /> The newer Ardiuno boards auto-reset when the serial connection is established which causes problems with OLA. To disable the auto-reset connect a 110 ohm resistor between the RESET and 5V pins. Note that you need to remove this when you program your Arduino. In the picture above a switch is used for ease of programming.<br /> <br /> == Arduino Software==<br /> <br /> The sources can be downloaded by running<br /> <br /> <pre><br /> git clone https://code.google.com/p/linux-lighting.arduino-rgb-mixer/ arduino-rgb-mixer<br /> </pre><br /> <br /> To build the sources you'll need the Arduino development environment. That can be found at http://arduino.cc/en/Main/Software.<br /> <br /> The latest compiled version of the firmware is available at http://code.google.com/p/linux-lighting/downloads/list<br /> <br /> == Host Software==<br /> <br /> Download and install [[OLA]] (verion 0.8.9 or above) and [[QLC]] if you want a graphical frontend. See the documentation for either/both products for getting it installed. The device should show up as a [[DMX USB Pro]], the first three channel control the red, green & blue intensities.<br /> <br /> The image below shows the RDM settings page in OLA for this device.<br /> <br /> [[Image:RGB_Mixer_RDM_Control.png|center|200px]]<br /> <br /> == Future Work ==<br /> <br /> * Expand the PWM outputs with http://www.arduino.cc/playground/Learning/TLC5940<br /> <br /> <br /> [[Category:Articles]]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=USB_Protocol_Extensions&diff=3282 USB Protocol Extensions 2010-03-19T03:44:05Z

<p>216.239.45.4: </p> <hr /> <div>This documents the additional message types added to the [[Enttec]] [[DMX USB Pro]] protocol to support multiple device types. As the number of devices supporting the protocol grows, it becomes difficult for software like [[OLA]] to differentiate the device types. The ''Device Manufacturer'' & ''Device Name'' messages allow the host software to determine the device and know which set of messages it supports.<br /> <br /> == Other Solutions ==<br /> <br /> === USB Serial Number ===<br /> <br /> Enttec USB Pro devices have only started programming the serial numbers recently (>2008?).<br /> When using the standard USB Serial drivers on Mac & Linux, the host application doesn't have access to the serial numbers. This would require us to write our own USB drivers using libusb to expose this information.<br /> <br /> === Use the User Addressable EEPROM ===<br /> <br /> Some devices don't support the ''Set Widget Parameters'' message so this isn't an option. Also it suffers from the bootstrapping issue, we need to know what device it is before we can write the information about what device it is...<br /> <br /> <br /> == Device Manufacturer, Label = 77, no data ==<br /> <br /> This message requests the device manufacturer information from the widget. The response is of the form:<br /> <br /> {| border=1<br /> ! '''Size in Bytes'''!! Description <br /> |-<br /> || 2 || [[ESTA]] ID, Most significant byte first<br /> |-<br /> || 32 || Up to 32 bytes containing the manufacturer name. Not null terminated.<br /> |}<br /> <br /> <br /> == Device Name, Label = 78, no data ==<br /> <br /> This message requests the device name information from the widget. The response is of the form:<br /> <br /> {| border=1<br /> ! '''Size in Bytes'''!! Description <br /> |-<br /> || 2 || Device Type ID, Manufacturer assigned. Most significant byte first.<br /> |-<br /> || 32 || Up to 32 bytes containing the device type. Not null terminated.<br /> |}<br /> <br /> <br /> == Devices Supporting these Message Types ==<br /> <br /> * [[Arduino RGB Mixer]] , ESTA ID: 0x7a70, Device ID: 0x1<br /> * [[DMX-TRI]], ESTA ID: 0x6864, Device ID 0x0:<br /> * [[DMXking USB DMX512-A]], ESTA ID: 0x6A6B, Device ID: 0x0<br /> <br /> == External References ==<br /> <br /> * [http://www.enttec.com/docs/dmx_usb_pro_api_spec.pdf DMX Pro API]<br /> * [http://www.esta.org/tsp/working_groups/CP/mfctrIDs.php ESTA IDs]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_Linux&diff=3054 OLA on Linux 2009-11-12T03:47:44Z

<p>216.239.45.4: /* Install libraries */</p> <hr /> <div>=Installing OLA on Linux From GIT/Archive=<br /> <br /> This describes how to get OLA working on a Linux system.<br /> <br /> ==Checkout or Download an Archive==<br /> <br /> git clone http://www.nomis52.net/git/lla<br /> <br /> If you don't have it yet, install '''git''' using your distro's package manager.<br /> <br /> ==Install libraries==<br /> <br /> You need a couple of libraries installed for everything to work correctly. Some of these are available as packages in most distros but others need to be downloaded.<br /> <br /> First up we'll need '''microhttpd''' for the embedded web server (Note: you'll need version >= 0.4.0):<br /> <br /> -> [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/]<br /> <br /> Then you will need '''libcppunit-dev''' and '''libcppunit'''.<br /> <br /> Debian users can install them with apt:<br /> <br /> apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev<br /> <br /> Next, you need the '''Protocol Buffers''' from Google (BSD license). Most likely, you will need to download and build them yourself:<br /> <br /> -> [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/]<br /> <br /> Debian users will can use the following packets (not yet in stable):<br /> libprotobuf2, libprotobuf-dev, protobuf-compiler<br /> <br /> <br /> Then, build '''CTemplate''' (another Google goodie):<br /> <br /> -> [http://code.google.com/p/google-ctemplate/ http://code.google.com/p/google-ctemplate/]<br /> <br /> Finally run ldconfig as root to pick up the new libraries<br /> <br /> ldconfig<br /> <br /> ==Configure==<br /> <br /> If you checked out the sources from git, you'll need to run<br /> <br /> autoreconf -i<br /> <br /> After that run<br /> <br /> ./configure<br /> <br /> ==Building & Testing==<br /> <br /> Build<br /> make<br /> <br /> <br /> If you get an error like the following:<br /> <br /> /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/ -g -O2 -c -o ltdl.lo ltdl.c<br /> ./libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found<br /> libtool: Version mismatch error. This is libtool 2.2.6, but the<br /> libtool: definition of this LT_INIT comes from an older release.<br /> libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6<br /> libtool: and run autoconf again.<br /> <br /> Your system uses a different version of libtool. Run:<br /> <br /> libtoolize --ltdl -c -f<br /> <br /> and then start from the autoreconf step again.<br /> <br /> Run the tests<br /> make check<br /> <br /> And install OLA<br /> sudo make install<br /> sudo ldconfig</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=For_Sale&diff=3030 For Sale 2009-08-15T18:58:15Z

<p>216.239.45.4: </p> <hr /> <div>The rules are simple - add items in the format:<br /> <br /> '''Item - $price - contact email - d/m/y added'''<br><br /> Description, be sure to mention the location.<br /> <br /> Any unsold items will be removed after a month.<br /> <br /> <br /> ----<br /> <br /> <br /> '''KSD250 Lamp (MSD 250) x 2 - $45 each - webspam <at> nomis52.net - 15/8/2009'''<br><br /> 2 KSD250 lamps, one of them has been used once to test a fixture, the other is brand new.<br /> [http://www.divinelighting.com/philips-msd-2502-277210-277210-lamp-bulb-p-328.html Link]. Located in CA.</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=For_Sale&diff=3029 For Sale 2009-08-15T18:57:23Z

<p>216.239.45.4: Created page with 'The rules are simple - add items in the format: '''Item - $price - contact email - d/m/y added'''<br> Description Any unsold items will be removed after a month. ---- '''KS…'</p> <hr /> <div>The rules are simple - add items in the format:<br /> <br /> '''Item - $price - contact email - d/m/y added'''<br><br /> Description<br /> <br /> Any unsold items will be removed after a month.<br /> <br /> <br /> ----<br /> <br /> <br /> '''KSD250 Lamp (MSD 250) x 2 - $45 each - webspam <at> nomis52.net - 15/8/2009'''<br><br /> 2 KSD250 lamps, one of them has been used once to test a fixture, the other is brand new.<br /> [http://www.divinelighting.com/philips-msd-2502-277210-277210-lamp-bulb-p-328.html Link]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OpenDMX.net&diff=3028 OpenDMX.net 2009-08-15T18:47:46Z

<p>216.239.45.4: </p> <hr /> <div><br /> {{News}}<br /> Welcome to opendmx.net. This site aims to be a resource for those involved in the lighting industry looking for DMX software and associated control systems. It's also home to documentation for various open source and free lighting software.<br /> <br /> <br /> If you're new to the world of lighting check out the [[:Category:Definitions|Definitions]] page, or have a look at the list of [[:Category:USB | USB interfaces]] or [[:Category:Controllers|Software Controllers]].<br /> <br /> Do you know of non-conforming or fussy DMX equipment? If so, please add it to the [[NonConformDMX]] page. Are you interesting in seeing what equipment and solutions are available? See the list of upcoming [[Conferences & Exhibitions]].<br /> <br /> Check out the [[For Sale]] section if you're looking for cheap equipment.<br /> <br /> For questions about the site, contact admin <AT> opendmx.net<br /> <br /> <br /> <center>[[Old News]]</center><br /> <br /> __NOTOC__</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Libartnet&diff=3019 Libartnet 2009-08-08T19:44:53Z

<p>216.239.45.4: </p> <hr /> <div>Link: http://code.google.com/p/linux-lighting/<br><br /> {{Features|linux=yes|osx=yes|rdm=yes|free=yes}}<br /> <br /> <br /> libartnet is a implementation of the [[ArtNet]] protocol designed for Unix-like systems and part of the [[OLA|Open Lighting Architecture]]. The artnet-examples package provides sample programs demonstrating the use of the library. Of particular interest is artnet_usb which allows ArtNet to DMX conversion by using the Enttec [[Open DMX USB]].<br /> <br /> <b>Related Tutorials:</b><br /> * [[LLA Sandnet Tutorial]]<br /> * [[LLA and Q Light Controller Ubuntu Tutorial]]<br /> * [[Linux ArtNet Node]]<br /> * [[Libartnet on Windows]]<br /> <br /> <b>Related Products:</b><br /> * [[OLA]]<br /> * [[Open DMX USB]]<br /> <br /> <br /> [[Category:Drivers / Libraries]]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Download_OLA&diff=2968 Download OLA 2009-08-03T01:46:38Z

<p>216.239.45.4: </p> <hr /> <div>Sources (via git) - this will download version [[LLA 0.3]]<br /> <br /> http://www.nomis52.net/git/lla<br /> http://www.nomis52.net/git/lla-examples<br /> <br /> Tarball:<br /> <br /> http://code.google.com/p/linux-lighting/downloads/list<br /> <br /> RPMS (probably out of date):<br /> <br /> http://rpms.netmindz.net/<br /> <br /> Live CD (iso) (really old):<br /> <br /> [https://sourceforge.net/project/showfiles.php?group_id=126566&package_id=192352 Sourceforge]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=D::Light&diff=2942 D::Light 2009-07-21T13:44:55Z

<p>216.239.45.4: </p> <hr /> <div>Link: http://www.nicole-banana.com/ <br><br /> [[Image:DL.png|300px|right]]<br /> {{Features|win=yes|osx=yes|tx=yes}}<br /> <br /> <br /> D::Light is a software designed for theater lighting. <br /> It currently both works on OS X and windows XP<br /> <br /> Art-Net support is added but only tested on osx.<br /> <br><br /> <br><br /> <br /> [[Category:Controllers]]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OpenDMX.net&diff=2937 OpenDMX.net 2009-07-21T00:55:30Z

<p>216.239.45.4: </p> <hr /> <div><br /> {{News}}<br /> Welcome to opendmx.net. This site aims to be a resource for those involved in the lighting industry looking DMX software and the associated control systems. It's also home to documentation for various open source and free lighting software.<br /> <br /> <br /> If you're new to the world of lighting check out the [[:Category:Definitions|Definitions]] page, or have a look at the list of [[:Category:USB | USB interfaces]] or [[:Category:Controllers|Software Controllers]].<br /> <br /> Do you know of non-conforming or fussy equipment? Add it to the [[NonConformDMX]] page. Are you interesting in seeing what equipment and solutions are available? See the list of upcoming [[Conferences & Exhibitions]].<br /> <br /> For questions about the site, contact admin <AT> opendmx.net<br /> <br /> <br /> <center>[[Old News]]</center><br /> <br /> __NOTOC__</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Conferences_%26_Exhibitions&diff=2936 Conferences & Exhibitions 2009-07-21T00:53:29Z

<p>216.239.45.4: Created page with '== LDI 2009 == Orlando, FL, USA<br> 16 - 22 November 2009<br> http://www.ldishow.com == PLASA09== London, UK<br> 13 - 16 September 2009<br> http://www.plasashow.com == USITT …'</p> <hr /> <div>== LDI 2009 ==<br /> Orlando, FL, USA<br><br /> 16 - 22 November 2009<br><br /> http://www.ldishow.com<br /> <br /> <br /> == PLASA09==<br /> London, UK<br><br /> 13 - 16 September 2009<br><br /> http://www.plasashow.com<br /> <br /> <br /> == USITT 2010==<br /> Kansas City, MO, USA<br><br /> March 30 - April 3<br><br /> http://www.usitt.org/2010/</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Libartnet_on_Windows&diff=2934 Libartnet on Windows 2009-07-20T15:55:04Z

<p>216.239.45.4: /* Install Mingw, msys & build tools */</p> <hr /> <div>Written by sl1200mk2 2009/07/01.<br /> (nicole-banana.com)<br /> <br /> This HOWTO outlines a method for compiling libartnet on Windows using MinGW to produce the libartnet-1.dll.<br /> <br /> <br /> == Install Mingw, msys & build tools ==<br /> <br /> The instructions at http://www.mingw.org/wiki/MSYS are very helpful. There are similar instructions at http://www.cccp-project.net/wiki/index.php?title=Installing_MSYS-MinGW<br /> <br /> * Install mingw and msys<br /> <br /> * Download these packages<br /> ** autoconf [http://ftp.gnu.org/gnu/autoconf/] <br /> ** automake [http://ftp.gnu.org/gnu/automake/]<br /> ** libtool [http://ftp.gnu.org/gnu/libtool/]<br /> <br /> * Launch the msys shell<br /> <br /> * Unpack autoconf, automake and libtool to a directory of your choice.<br /> <br /> * Install each of them with the following command:<br /> <br /> $ ./configure --prefix=/mingw && make && make install<br /> <br /> * Update PKG_CONFIG_PATH<br /> <br /> As all the libraries will be installed in /mingw, PKG_CONFIG_PATH must be set. <br /> <br /> Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:<br /> <br /> PKG_CONFIG_PATH="/mingw/lib/pkgconfig"<br /> <br /> You might also want to set CFLAGS. Safe options for MinGW are:<br /> <br /> CFLAGS="-pipe -O2 -mms-bitfields -march=i686"<br /> <br /> just before<br /> <br /> export HOME LOGNAME MSYSTEM HISTFILE<br /> <br /> and modify that line by adding the variables:<br /> <br /> export HOME LOGNAME MSYSTEM HISTFILE CFLAGS PKG_CONFIG_PATH<br /> <br /> Now restart MSYS. You should now be able to use MSYS without problems.<br /> <br /> This is the biggest part of the job.<br /> <br /> == Install Git ==<br /> <br /> See http://code.google.com/p/msysgit/, be sure to select "unix style carriage returns" otherwise you'll get autoconf errors.<br /> <br /> == Download Libartnet ==<br /> <br /> Grab the libarnet sources (via the git shell or the git UI)<br /> <br /> $ git clone http://www.nomis52.net/git/libartnet<br /> <br /> == Compile Libartnet ==<br /> <br /> $ cd libartnet<br /> $ autoreconf -i -f <br /> $ ./configure --prefix=/mingw && make && make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Libartnet_on_Windows&diff=2933 Libartnet on Windows 2009-07-20T15:54:39Z

<p>216.239.45.4: /* Compile Libartnet */</p> <hr /> <div>Written by sl1200mk2 2009/07/01.<br /> (nicole-banana.com)<br /> <br /> This HOWTO outlines a method for compiling libartnet on Windows using MinGW to produce the libartnet-1.dll.<br /> <br /> <br /> == Install Mingw, msys & build tools ==<br /> <br /> The instructions at http://www.mingw.org/wiki/MSYS are very helpful.<br /> <br /> * Install mingw and msys<br /> <br /> * Download these packages<br /> ** autoconf [http://ftp.gnu.org/gnu/autoconf/] <br /> ** automake [http://ftp.gnu.org/gnu/automake/]<br /> ** libtool [http://ftp.gnu.org/gnu/libtool/]<br /> <br /> * Launch the msys shell<br /> <br /> * Unpack autoconf, automake and libtool to a directory of your choice.<br /> <br /> * Install each of them with the following command:<br /> <br /> $ ./configure --prefix=/mingw && make && make install<br /> <br /> * Update PKG_CONFIG_PATH<br /> <br /> As all the libraries will be installed in /mingw, PKG_CONFIG_PATH must be set. <br /> <br /> Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:<br /> <br /> PKG_CONFIG_PATH="/mingw/lib/pkgconfig"<br /> <br /> You might also want to set CFLAGS. Safe options for MinGW are:<br /> <br /> CFLAGS="-pipe -O2 -mms-bitfields -march=i686"<br /> <br /> just before<br /> <br /> export HOME LOGNAME MSYSTEM HISTFILE<br /> <br /> and modify that line by adding the variables:<br /> <br /> export HOME LOGNAME MSYSTEM HISTFILE CFLAGS PKG_CONFIG_PATH<br /> <br /> Now restart MSYS. You should now be able to use MSYS without problems.<br /> <br /> This is the biggest part of the job.<br /> <br /> == Install Git ==<br /> <br /> See http://code.google.com/p/msysgit/, be sure to select "unix style carriage returns" otherwise you'll get autoconf errors.<br /> <br /> == Download Libartnet ==<br /> <br /> Grab the libarnet sources (via the git shell or the git UI)<br /> <br /> $ git clone http://www.nomis52.net/git/libartnet<br /> <br /> == Compile Libartnet ==<br /> <br /> $ cd libartnet<br /> $ autoreconf -i -f <br /> $ ./configure --prefix=/mingw && make && make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OpenDMX.net&diff=2900 OpenDMX.net 2009-07-13T20:14:57Z

<p>216.239.45.4: </p> <hr /> <div><br /> {{News}}<br /> Welcome to opendmx.net. This site aims to be a resource for those involved in the lighting industry looking DMX software and the associated control systems. It's also home to documentation for various open source and free lighting software.<br /> <br /> <br /> If you're new to the world of lighting check out the [[:Category:Definitions|Definitions]] page, or check out the list of [[:Category:USB | USB interfaces]] or [[:Category:Controllers|Software Controllers]].<br /> <br /> Do you know of non-conforming or fussy equipment? Add it to the [[NonConformDMX]] page.<br /> <br /> For questions about the site, contact admin <AT> opendmx.net<br /> <br /> <br /> <center>[[Old News]]</center><br /> <br /> __NOTOC__</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Template:NewsHeading&diff=2830 Template:NewsHeading 2009-07-11T00:13:37Z

<p>216.239.45.4: </p> <hr /> <div>style="border-top: 1px solid #999;" bgcolor="#C5D8FC" align="center"</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Template:NewsHeading&diff=2829 Template:NewsHeading 2009-07-11T00:12:55Z

<p>216.239.45.4: New page: bgcolor="#A7C1F2" align="center"</p> <hr /> <div>bgcolor="#A7C1F2" align="center"</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Libartnet_on_Windows&diff=2793 Libartnet on Windows 2009-07-02T00:24:26Z

<p>216.239.45.4: /* Compile Libartnet */</p> <hr /> <div>Written by sl1200mk2 2009/07/01.<br /> (nicole-banana.com)<br /> <br /> This HOWTO outlines a method for compiling libartnet on Windows using MinGW to produce the libartnet-1.dll.<br /> <br /> <br /> == Install Mingw, msys & build tools ==<br /> <br /> The instructions at http://www.mingw.org/wiki/MSYS are very helpful.<br /> <br /> * Install mingw and msys<br /> <br /> * Download these packages<br /> ** autoconf [http://ftp.gnu.org/gnu/autoconf/] <br /> ** automake [http://ftp.gnu.org/gnu/automake/]<br /> ** libtool [http://ftp.gnu.org/gnu/libtool/]<br /> <br /> * Launch the msys shell<br /> <br /> * Unpack autoconf, automake and libtool to a directory of your choice.<br /> <br /> * Install each of them with the following command:<br /> <br /> $ ./configure --prefix=/mingw && make && make install<br /> <br /> * Update PKG_CONFIG_PATH<br /> <br /> As all the libraries will be installed in /mingw, PKG_CONFIG_PATH must be set. <br /> <br /> Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:<br /> <br /> PKG_CONFIG_PATH="/mingw/lib/pkgconfig"<br /> <br /> You might also want to set CFLAGS. Safe options for MinGW are:<br /> <br /> CFLAGS="-pipe -O2 -mms-bitfields -march=i686"<br /> <br /> just before<br /> <br /> export HOME LOGNAME MSYSTEM HISTFILE<br /> <br /> and modify that line by adding the variables:<br /> <br /> export HOME LOGNAME MSYSTEM HISTFILE CFLAGS PKG_CONFIG_PATH<br /> <br /> Now restart MSYS. You should now be able to use MSYS without problems.<br /> <br /> This is the biggest part of the job.<br /> <br /> == Install Git ==<br /> <br /> See http://code.google.com/p/msysgit/, be sure to select "unix style carriage returns" otherwise you'll get autoconf errors.<br /> <br /> == Download Libartnet ==<br /> <br /> Grab the libarnet sources (via the git shell or the git UI)<br /> <br /> $ git clone http://www.nomis52.net/git/libartnet<br /> <br /> == Compile Libartnet ==<br /> <br /> $ cd libartnet<br /> $ autoreconf -i -f <br /> $ ./configure --prefix=/c/MinGW/ && make && make install<br /> <br /> <br /> AC_PROG_LIBTOOL macro and -no-undefined flag cause libartnet to build as DLL</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_OS_X&diff=2782 OLA on OS X 2009-06-24T01:23:01Z

<p>216.239.45.4: /* Set some env vars */</p> <hr /> <div>This page describes how to get LLA 0.3 working on OS X. <br /> <br /> == Basic setup ==<br /> <br /> * Install xcode [[http://developer.apple.com/technology/xcode.html]]<br /> * install git [[http://code.google.com/p/git-osx-installer/]]<br /> * install mac ports [[http://www.macports.org/]]<br /> <br /> == Use Mac Ports to install stuff==<br /> <br /> $ port install pkgconfig cppunit unittest-cpp protobuf-cpp <br /> <br /> == Set some env vars==<br /> <br /> set $PATH to point to something sane (you should also make sure you point it at your ctemplate and libmicrohttpd)<br /> <br /> export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig<br /> export CPPFLAGS="-I/opt/local/include/"<br /> export LDFLAGS="-L/opt/local/lib/"<br /> <br /> == Optionally install microhttpd and ctemplate==<br /> <br /> If you want the http interface you need these<br /> <br /> * http://www.gnu.org/software/libmicrohttpd/ [>= 0.4] (Currently you need to install libgcrypt too for this library to work)<br /> sudo port install libgcrypt<br /> or you can disable https support (which should work with LLA just fine) by using the configure line "./configure --enable-https=no"<br /> * http://code.google.com/p/google-ctemplate/<br /> <br /> * Make sure both of these are made AND installed before running "./configure" on LLA otherwise it will not detect the libraries and ignore all the HTTP server code<br /> <br /> == Checkout LLA ==<br /> <br /> git clone http://www.nomis52.net/git/lla<br /> cd lla<br /> <br /> == Run reautoconf==<br /> <br /> If this is the first time run with -i to install the missing files<br /> <br /> autoreconf -i<br /> <br /> == Do the usual steps==<br /> <br /> ./configure<br /> make<br /> make check<br /> sudo make install<br /> <br /> If you get an error like the following:<br /> <br /> /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/ -g -O2 -c -o ltdl.lo ltdl.c<br /> ./libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found<br /> libtool: Version mismatch error. This is libtool 2.2.6, but the<br /> libtool: definition of this LT_INIT comes from an older release.<br /> libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6<br /> libtool: and run autoconf again.<br /> <br /> Your system uses a different version of libtool. Run:<br /> <br /> glibtoolize --ltdl -c -f<br /> <br /> and then start from the autoreconf step again.</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_OS_X&diff=2781 OLA on OS X 2009-06-24T01:03:21Z

<p>216.239.45.4: </p> <hr /> <div>This page describes how to get LLA 0.3 working on OS X. <br /> <br /> == Basic setup ==<br /> <br /> * Install xcode [[http://developer.apple.com/technology/xcode.html]]<br /> * install git [[http://code.google.com/p/git-osx-installer/]]<br /> * install mac ports [[http://www.macports.org/]]<br /> <br /> == Use Mac Ports to install stuff==<br /> <br /> $ port install pkgconfig cppunit unittest-cpp protobuf-cpp <br /> <br /> == Set some env vars==<br /> <br /> set $PATH to point to something sane (you should also make sure you point it at your ctemplate and libmicrohttpd)<br /> <br /> export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig<br /> export CPPFLAGS="-I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/"<br /> export LDFLAGS="-L/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/lib/"<br /> <br /> <br /> == Optionally install microhttpd and ctemplate==<br /> <br /> If you want the http interface you need these<br /> <br /> * http://www.gnu.org/software/libmicrohttpd/ [>= 0.4] (Currently you need to install libgcrypt too for this library to work)<br /> sudo port install libgcrypt<br /> or you can disable https support (which should work with LLA just fine) by using the configure line "./configure --enable-https=no"<br /> * http://code.google.com/p/google-ctemplate/<br /> <br /> * Make sure both of these are made AND installed before running "./configure" on LLA otherwise it will not detect the libraries and ignore all the HTTP server code<br /> <br /> == Checkout LLA ==<br /> <br /> git clone http://www.nomis52.net/git/lla<br /> cd lla<br /> <br /> == Run reautoconf==<br /> <br /> If this is the first time run with -i to install the missing files<br /> <br /> autoreconf -i<br /> <br /> == Do the usual steps==<br /> <br /> ./configure<br /> make<br /> make check<br /> sudo make install<br /> <br /> If you get an error like the following:<br /> <br /> /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/ -g -O2 -c -o ltdl.lo ltdl.c<br /> ./libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found<br /> libtool: Version mismatch error. This is libtool 2.2.6, but the<br /> libtool: definition of this LT_INIT comes from an older release.<br /> libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6<br /> libtool: and run autoconf again.<br /> <br /> Your system uses a different version of libtool. Run:<br /> <br /> glibtoolize --ltdl -c -f<br /> <br /> and then start from the autoreconf step again.</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_OS_X&diff=2780 OLA on OS X 2009-06-24T00:42:06Z

<p>216.239.45.4: </p> <hr /> <div>This page describes how to get LLA 0.3 working on OS X. <br /> <br /> == Basic setup ==<br /> <br /> * Install xcode [[http://developer.apple.com/technology/xcode.html]]<br /> * install git [[http://code.google.com/p/git-osx-installer/]]<br /> * install mac ports [[http://www.macports.org/]]<br /> <br /> == Use Mac Ports to install stuff==<br /> <br /> $ port install pkgconfig cppunit unittest-cpp<br /> <br /> == Set some env vars==<br /> <br /> set $PATH to point to something sane (you should also make sure you point it at your ctemplate and libmicrohttpd)<br /> <br /> export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig<br /> export CPPFLAGS="-I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/"<br /> export LDFLAGS="-L/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/lib/"<br /> <br /> == Installed protobuf libraries ==<br /> <br /> http://code.google.com/p/protobuf/<br /> <br /> <br /> == Optionally install microhttpd and ctemplate==<br /> <br /> If you want the http interface you need these<br /> <br /> * http://www.gnu.org/software/libmicrohttpd/ [>= 0.4] (Currently you need to install libgcrypt too for this library to work)<br /> sudo port install libgcrypt<br /> or you can disable https support (which should work with LLA just fine) by using the configure line "./configure --enable-https=no"<br /> * http://code.google.com/p/google-ctemplate/<br /> <br /> * Make sure both of these are made AND installed before running "./configure" on LLA otherwise it will not detect the libraries and ignore all the HTTP server code<br /> <br /> == Checkout LLA ==<br /> <br /> git clone http://www.nomis52.net/git/lla<br /> cd lla<br /> <br /> == Run reautoconf==<br /> <br /> If this is the first time run with -i to install the missing files<br /> <br /> autoreconf -i<br /> <br /> == Do the usual steps==<br /> <br /> ./configure<br /> make<br /> make check<br /> sudo make install<br /> <br /> If you get an error like the following:<br /> <br /> /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/ -g -O2 -c -o ltdl.lo ltdl.c<br /> ./libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found<br /> libtool: Version mismatch error. This is libtool 2.2.6, but the<br /> libtool: definition of this LT_INIT comes from an older release.<br /> libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6<br /> libtool: and run autoconf again.<br /> <br /> Your system uses a different version of libtool. Run:<br /> <br /> glibtoolize --ltdl -c -f<br /> <br /> and then start from the autoreconf step again.</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_OS_X&diff=2779 OLA on OS X 2009-06-24T00:38:28Z

<p>216.239.45.4: /* Use Mac Ports to install stuff */</p> <hr /> <div>This page describes how to get LLA 0.3 working on OS X. <br /> <br /> == Basic setup ==<br /> <br /> * Install xcode [[http://developer.apple.com/technology/xcode.html]]<br /> * install git [[http://code.google.com/p/git-osx-installer/]]<br /> * install mac ports [[http://www.macports.org/]]<br /> <br /> == Use Mac Ports to install stuff==<br /> <br /> $ port install pkgconfig cppunit unittest-cpp<br /> <br /> == Set some env vars==<br /> <br /> set $PATH to point to something sane (you should also make sure you point it at your ctemplate and libmicrohttpd)<br /> <br /> export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig<br /> export CPPFLAGS="-I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/"<br /> export LDFLAGS="-L/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/lib/"<br /> <br /> == Optionally install microhttpd and ctemplate==<br /> <br /> If you want the http interface you need these<br /> <br /> * http://www.gnu.org/software/libmicrohttpd/ [>= 0.4] (Currently you need to install libgcrypt too for this library to work)<br /> sudo port install libgcrypt<br /> or you can disable https support (which should work with LLA just fine) by using the configure line "./configure --enable-https=no"<br /> * http://code.google.com/p/google-ctemplate/<br /> <br /> * Make sure both of these are made AND installed before running "./configure" on LLA otherwise it will not detect the libraries and ignore all the HTTP server code<br /> <br /> == Checkout LLA ==<br /> <br /> git clone http://www.nomis52.net/git/lla<br /> cd lla<br /> <br /> == Run reautoconf==<br /> <br /> If this is the first time run with -i to install the missing files<br /> <br /> autoreconf -i<br /> <br /> == Do the usual steps==<br /> <br /> ./configure<br /> make<br /> make check<br /> sudo make install<br /> <br /> If you get an error like the following:<br /> <br /> /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/ -g -O2 -c -o ltdl.lo ltdl.c<br /> ./libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found<br /> /Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found<br /> libtool: Version mismatch error. This is libtool 2.2.6, but the<br /> libtool: definition of this LT_INIT comes from an older release.<br /> libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6<br /> libtool: and run autoconf again.<br /> <br /> Your system uses a different version of libtool. Run:<br /> <br /> glibtoolize --ltdl -c -f<br /> <br /> and then start from the autoreconf step again.</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_OS_X&diff=2722 OLA on OS X 2009-05-06T16:46:06Z

<p>216.239.45.4: /* Run reautoconf */</p> <hr /> <div>This page describes how to get LLA 0.3 working on OS X. <br /> <br /> == Basic setup ==<br /> <br /> * Install xcode [[http://developer.apple.com/technology/xcode.html]]<br /> * install git [[http://code.google.com/p/git-osx-installer/]]<br /> * install mac ports [[http://www.macports.org/]]<br /> <br /> == Use Mac Ports to install stuff==<br /> <br /> $ port install pkgconfig protobuf-cpp cppunit unittest-cpp libtool<br /> <br /> == Set some env vars==<br /> <br /> set $PATH to point to something sane (you should also make sure you point it at your ctemplate and libmicrohttpd)<br /> <br /> export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig<br /> export CPPFLAGS="-I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/"<br /> export LDFLAGS="-L/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/lib/"<br /> <br /> == Optionally install microhttpd and ctemplate==<br /> <br /> If you want the http interface you need these<br /> <br /> * http://www.gnu.org/software/libmicrohttpd/ [>= 0.4] (Currently you need to install libgcrypt too for this library to work)<br /> sudo port install libgcrypt<br /> or you can disable https support (which should work with LLA just fine) by using the configure line "./configure --enable-https=no"<br /> * http://code.google.com/p/google-ctemplate/<br /> <br /> * Make sure both of these are made AND installed before running "./configure" on LLA otherwise it will not detect the libraries and ignore all the HTTP server code<br /> <br /> == Checkout LLA ==<br /> <br /> git clone http://www.nomis52.net/git/lla<br /> cd lla<br /> <br /> == Run reautoconf==<br /> <br /> If this is the first time run with -i to install the missing files<br /> <br /> autoreconf -i<br /> <br /> == Do the usual steps==<br /> <br /> ./configure<br /> make<br /> make check<br /> sudo make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_OS_X&diff=2721 OLA on OS X 2009-05-06T16:45:42Z

<p>216.239.45.4: /* Run autoconf */</p> <hr /> <div>This page describes how to get LLA 0.3 working on OS X. <br /> <br /> == Basic setup ==<br /> <br /> * Install xcode [[http://developer.apple.com/technology/xcode.html]]<br /> * install git [[http://code.google.com/p/git-osx-installer/]]<br /> * install mac ports [[http://www.macports.org/]]<br /> <br /> == Use Mac Ports to install stuff==<br /> <br /> $ port install pkgconfig protobuf-cpp cppunit unittest-cpp libtool<br /> <br /> == Set some env vars==<br /> <br /> set $PATH to point to something sane (you should also make sure you point it at your ctemplate and libmicrohttpd)<br /> <br /> export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig<br /> export CPPFLAGS="-I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/"<br /> export LDFLAGS="-L/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/lib/"<br /> <br /> == Optionally install microhttpd and ctemplate==<br /> <br /> If you want the http interface you need these<br /> <br /> * http://www.gnu.org/software/libmicrohttpd/ [>= 0.4] (Currently you need to install libgcrypt too for this library to work)<br /> sudo port install libgcrypt<br /> or you can disable https support (which should work with LLA just fine) by using the configure line "./configure --enable-https=no"<br /> * http://code.google.com/p/google-ctemplate/<br /> <br /> * Make sure both of these are made AND installed before running "./configure" on LLA otherwise it will not detect the libraries and ignore all the HTTP server code<br /> <br /> == Checkout LLA ==<br /> <br /> git clone http://www.nomis52.net/git/lla<br /> cd lla<br /> <br /> == Run reautoconf==<br /> <br /> If this is the first time run with -i to install the missing files<br /> <br /> autoreconf -i<br /> [[Link title]]<br /> <br /> == Do the usual steps==<br /> <br /> ./configure<br /> make<br /> make check<br /> sudo make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_Device_Specific_Configuration&diff=2699 OLA Device Specific Configuration 2009-03-03T06:24:33Z

<p>216.239.45.4: </p> <hr /> <div>==StageProfi==<br /> <br /> This comes in two flavors, a USB model and an Ethernet/IP model.<br /> <br /> device = /dev/ttyUSB0<br /> device = 192.168.1.250<br /> <br /> <br /> ==USB Pro==<br /> <br /> ===Mac===<br /> <br /> Make sure you install the drives: http://www.ftdichip.com/Drivers/VCP.htm<br /> <br /> After a restart run:<br /> <br /> ls /dev/cu.usbserial-*<br /> <br /> And add the path to you ~/.lla/lla-usbpro.conf file: <br /> <br /> device = /dev/cu.usbserial-0000101D</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Using_OLA&diff=2698 Using OLA 2009-03-02T19:59:25Z

<p>216.239.45.4: /* How to start llad */</p> <hr /> <div>== About LLA ==<br /> <br /> [[LLA]] is a framework that allows applications to send and receive DMX using various hardware devices and DMX over IP protocols. Hardware devices and protocols can also be connected together and LLA will route the DMX between the two.<br /> <br /> LLA consists of 4 parts:<br /> - the lla daemon (llad)<br /> - the lla client library (liblla)<br /> - various lla plugins (libllaX)<br /> - example programs (lla_dev_info, lla_patch etc.)<br /> <br /> == LLA Terminology ==<br /> <br /> ; Port (noun)<br /> : A port represents up to 512 DMX channels that sends data (OUT port) or receives data (IN port). It can be either a physical port on a device or a virtual port created by a DMX over IP protocol.<br /> <br /> ; Device (noun)<br /> : A device is a group of ports, for example some devices might have an input and output port.<br /> <br /> ; Plugin (noun)<br /> :A LLA plugin supports a group of physical devices or a DMX over IP protocol. Example plugins include ArtNet, ShowNet, EspNet, DmxUsbPro, OpenDmx, StageProfi, Dmx4Linux etc. On startup plugins look for the devices they are responsible for and set them up.<br /> <br /> ; Universe (noun)<br /> : A universe is a set of 512 DMX channels. Ports can be patched to universes in which case they'll either send the data for the universe (in the case of output ports) or set the values for the universe (for input ports)<br /> <br /> ; Client (noun)<br /> : A client is another application that connects to LLA using liblla.<br /> <br /> ; Patch (verb)<br /> : The act of assigning a port to a universe.<br /> <br /> == Using LLA ==<br /> <br /> In the general case you want to:<br /> - start the lla daemon<br /> - patch some output ports to universes<br /> - patch an input port or run a client application<br /> <br /> === How to start llad ===<br /> <br /> For testing run llad in non-forking, log to stdout, debug level 3:<br /> <br /> llad -l 3<br /> <br /> '''Do not run this as root'''. If LLA doesn't work as your user it's due to incorrect permissions on files within /dev - fix them and try again. I repeat do not run this as root.<br /> <br /> === How to setup an interface ===<br /> <br /> Before an interface (e.g. a USB dongle) can be used, a ''port'' on the ''device'' must be ''patched'' to a ''universe''.<br /> <br /> First run lla_dev_info and find out what device / port the desired interface has:<br /> <br /> $ lla_dev_info<br /> Device 0: Art-Net Device<br /> port 0, cap IN<br /> port 1, cap IN<br /> port 2, cap IN<br /> port 3, cap IN<br /> port 4, cap OUT<br /> port 5, cap OUT<br /> port 6, cap OUT<br /> port 7, cap OUT<br /> Device 1: Stage Profi Device<br /> port 0, cap OUT<br /> <br /> In this case we want to use the StageProfi device so we patch device 1, port 0 to a new universe (1)<br /> <br /> Then the command '''lla_patch''' can be given the numbers just found and the desired universe, so they get connected.<br /> <br /> lla_patch -d 1 -p 0 -u 1<br /> <br /> Running lla_dev_info again shows us the patch has been made:<br /> <br /> $ lla_dev_info<br /> Device 0: Art-Net Device<br /> port 0, cap IN<br /> port 1, cap IN<br /> port 2, cap IN<br /> port 3, cap IN<br /> port 4, cap OUT<br /> port 5, cap OUT<br /> port 6, cap OUT<br /> port 7, cap OUT<br /> Device 1: Stage Profi Device<br /> port 0, cap OUT, universe 1<br /> <br /> Finally the setup can be tested with '''lla_dmxconsole''' or '''lla_dmxmonitor''' to set or receive DMX values.<br /> <br /> Command line options can be seen [http://nomis52.net/?section=projects&sect2=lla&page=llatools here].<br /> <br /> [[Category:Articles]]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_0.3&diff=2697 OLA 0.3 2009-03-02T19:57:44Z

<p>216.239.45.4: /* Other Docs */</p> <hr /> <div>This page discusses the development release of LLA (0.3).<br /> <br /> ==User facing changes==<br /> <br /> * (Optional) HTTP server with web interface for configuration<br /> * Web based dmx console<br /> * Support for embedding<br /> * OS X support<br /> <br /> ==Internal changes==<br /> <br /> * Completely new RPC system based on [[http://code.google.com/p/protobuf/ Protocol Buffers]] allowing for asynchronous rpcs from the client.<br /> * ExportMap<br /> <br /> ==Known Issues==<br /> <br /> Please report issues at http://code.google.com/p/linux-lighting/issues/list<br /> <br /> * Due to bugs in libmicrohttpd, you need version 0.4 and above for it to work correctly.<br /> <br /> ==Other Docs==<br /> <br /> * [[LLA on OS X]]<br /> * [[LLA on Debian]]<br /> * [[LLA Client API]]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Download_OLA&diff=2696 Download OLA 2009-03-02T19:56:26Z

<p>216.239.45.4: </p> <hr /> <div>Sources (via git) - this will download version [[LLA 0.3]]<br /> <br /> http://www.nomis52.net/git/lla<br /> http://www.nomis52.net/git/lla-examples<br /> <br /> Debian Packages (out of date):<br /> <br /> http://www.nomis52.net/data/debian<br /> <br /> RPMS (probably out of date):<br /> <br /> http://rpms.netmindz.net/<br /> <br /> Live CD (iso) (really old):<br /> <br /> [https://sourceforge.net/project/showfiles.php?group_id=126566&package_id=192352 Sourceforge]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=Open_Lighting_Architecture&diff=2695 Open Lighting Architecture 2009-03-02T19:53:51Z

<p>216.239.45.4: </p> <hr /> <div>Link: http://www.nomis52.net/?section=projects&sect2=lla&page=llaintro <br><br /> {{Features|free=yes|tx=yes|rx=yes|linux=yes|osx=yes}}<br /> [[Image:Llad_home.png|right]]<br /> <br /> <br /> LLA is a framework that allows applications to send and receive DMX, using various hardware devices and 'DMX over IP' protocols. It can make [[:Category:Controllers | software controllers]] talk to DMX hardware.<br /> <br /> LLA allows DMX sent using various DMX over IP protocols to be converted from one format to another. This enables devices from different manufacturers to talk to each another (for example a [[Strand_Lighting|Strand]] Console can send DMX to an [[Enttec]] [[DmxEtherGate MKII|EtherGate]]).<br /> <br /> <br /> [[LLA Live]] is a stand-alone bootable CD containing software from the Linux Lighting Architecture project.<br /> <br /> When combined with a physical DMX interface such as the [[DMX USB Pro]], LLA Live can send and receive data from traditional wired DMX networks.<br /> <br /> LLA can run on Linux with all its drivers, and on Mac OS X (but at the moment the drivers (LLA plugins) needs to be modified to work).<br /> A port to Windows is feasible, if someone wants to add the necessary code.<br /> <br /> <b>Bugs?</b>: Check the bug tracker at http://code.google.com/p/linux-lighting/issues/list<br /> <br /> <b>Questions?</b>: See the news group at http://groups.google.com/group/linux-lighting<br /> <br /> <br /> <b>Supported Devices/Protocols:</b><br /> <br /> {| border=1<br /> ! '''Driver'''!! Linux !! '''Mac OS X''' <br /> |-<br /> || [[:Category:ArtNet|ArtNet]] || Yes || Yes<br /> |-<br /> || [[:Category:ShowNet|ShowNet]] || Yes || ??<br /> |-<br /> || [[:Category:ESP Net|ESP Net]] || Yes || ??<br /> |-<br /> || [[:Category:Sandnet|Sandnet]] || Yes || ??<br /> |-<br /> || [[E1.31]] / [[ACN]] || underway || ??<br /> |-<br /> || [[DMX USB Pro]] || Yes || Yes<br /> |-<br /> || [[Open DMX USB]] || Yes || ??<br /> |-<br /> || [[StageProfi]] || Yes || ??<br /> |-<br /> || [[:Category:Pathport|Pathport]] || in testing || ??<br /> |-<br /> || [[DMX 4 Linux]] || Yes || -<br /> |}<br /> <br /> <br /> <b>Getting Started</b><br /> <br /> Start here if you've never used LLA before and read these in order.<br /> * [[Download LLA]]<br /> * [[Building LLA]] - How to get it compiled (old version)<br /> * [[Using LLA]] - A basic introduction<br /> * [[LLA Device Specific Configuration]]<br /> <br /> <b>Documentation:</b><br /> * [[LLA 0.3]] - The new release<br /> * [[LLA developer info]] - about the source code and structure<br /> * [[LLA Tips & Tricks]]<br /> * [[Using the Python libraries]] - easy DMX programming<br /> <br /> <b>Tutorials</b><br /> * [[LLA Sandnet Tutorial]] - Setup Horizon using Sandnet and LLA<br /> * [[LLA and Q Light Controller Ubuntu Tutorial]] - Setup LLA on Ubuntu/Debian-type distro with QLC<br /> <br /> <br /> LLA can also run on a wireless access point. [http://nomis52.net/?section=projects&sect2=artnet&page=node]<br /> <br /> There is a project underway to build packages for OpenWrt. See http://lists.culturebase.org/cgi-bin/mailman/listinfo/lla-openwrt for more details.<br /> <br /> <br /> [[Category:ArtNet]]<br /> [[Category:ESP Net]]<br /> [[Category:Sandnet]]<br /> [[Category:ShowNet]]<br /> [[Category:Utilities]]</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_Client_API&diff=2683 OLA Client API 2009-02-18T00:06:11Z

<p>216.239.45.4: </p> <hr /> <div>'''Note:''' This refers to the most recent version of LLA [>= 0.3.0]<br /> <br /> LLA provides a client library which allows other applications to send/receive DMX as well as control the LLA server. To cater for different application requirements, a ''SimpleClient'' helper class is provided which can be used to perform the client setup / management. <br /> <br /> ==Example I: Sending an DMX update==<br /> <br /> This first client simply connects to the LLA Server and sends one DMX update. It's about as simple as you can get because it requires no callbacks and exits immediately. We use two classes in this example, ''lla::SimpleClient'', and ''lla::LlaClient''.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> int main() {<br /> // some dummy dmx data<br /> dmx_t dmx_data[] = {0, 128, 255};<br /> <br /> lla::SimpleClient simple_client;<br /> if (!simple_client.Setup())<br /> //setup failed<br /> return -1;<br /> <br /> // Get the underlying LlaClient<br /> lla::LlaClient *client = simple_client.GetClient();<br /> <br /> // Send the DMX data <br /> client->SendDmx(1, dmx_data, sizeof(dmx_data));<br /> }<br /> <br /> <br /> The main class used to communicate with the LLA Server is ''LlaClient''. For ease of use, the ''SimpleClient'' class sets up ''LlaClient'' with a connection to an LLA Server running on the localhost:LLA_DEFAULT_PORT. You can call GetClient() on a ''SimpleClient'' instance to get a pointer to the underlying ''LlaClient''.<br /> <br /> <br /> ==Example II: Sending multiple updates==<br /> <br /> The previous example only sent a single DMX update before quitting. This next example adds a timeout which sends DMX every 50ms. This introduces a new class ''SelectServer'' which is used for registering timeouts.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> // Maximum value of a dmx channel<br /> static const unsigned int MAX_DMX = 255;<br /> // How often to send updates<br /> static const unsigned int TIMEOUT_MS = 50;<br /> <br /> class DmxTimeout: public lla::select_server::TimeoutListener {<br /> public:<br /> DmxTimeout(lla::LlaClient *client):<br /> TimeoutListener(), m_tick(0), m_client(client) {}<br /> <br /> // Called on timeout<br /> int Timeout() {<br /> m_dmx_data[0] = MAX_DMX;<br /> m_dmx_data[1] = m_tick;<br /> m_dmx_data[2] = MAX_DMX - m_tick;<br /> m_client->SendDmx(1, m_dmx_data, sizeof(m_dmx_data));<br /> m_tick++;<br /> m_tick %= MAX_DMX + 1;<br /> }<br /> private:<br /> unsigned int m_tick;<br /> dmx_t m_dmx_data[3];<br /> lla::LlaClient *m_client;<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::select_server::SelectServer *ss = simple_client.GetSelectServer();<br /> // Create a timeout and register it<br /> DmxTimeout timeout(simple_client.GetClient());<br /> ss->RegisterTimeout(TIMEOUT_MS, &timeout);<br /> <br /> // Start the main loop<br /> ss->Run();<br /> }<br /> <br /> <br /> In this example we create ''DmxTimeout'' class whose ''Timeout()'' method is called every time the timer expires. We use the ''Timeout()'' method to send DMX data.<br /> <br /> The other important part here is the ''SelectServer''. As well as the ''RegisterTimeout'' method we've used above, this can also be used to register sockets so we can respond to network activity. The ''Run()'' method starts the main event processing loop which will halt if an error occurs or ''Terminate()'' is called.<br /> <br /> <br /> ==Example III: Receiving DMX data==<br /> <br /> The third example shows how to listen and respond to event from the LLA server.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> static const unsigned int UNIVERSE = 1;<br /> <br /> class OurObserver: public lla::LlaClientObserver {<br /> public:<br /> // Called when new DMX values arrive<br /> void NewDmx(unsigned int universe, unsigned int length,<br /> dmx_t *data, const std::string &error) {<br /> printf("received %d channels for universe %d\n",<br /> length, universe);<br /> }<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> OurObserver observer;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::LlaClient *client = simple_client.GetClient();<br /> // Set the observer and register our interest in this universe<br /> client->SetObserver(&observer);<br /> client->RegisterUniverse(UNIVERSE, lla::REGISTER);<br /> simple_client.GetSelectServer()->Run();<br /> }<br /> <br /> <br /> Here we inherit from the ''LlaClientObserver'' class and override the methods we're interested in receiving notification for.<br /> <br /> In the main function we set the observer object and register our interest in a universe.<br /> <br /> <br /> ==Example IV: More complex client==<br /> <br /> The above is all well and good but what if the main application has it's own event processing loop? An example of this is a GTK/Glib application which uses GMainLoop.<br /> <br /> On the other hand, what if you're not connecting to the LLA Server over TCP? Sometimes it may be desirable to embed the LLA server within the main application.<br /> <br /> Bypassing the SimpleClient and using LlaClient directly addresses both these problems.<br /> <br /> #include <lla/LlaClient.h><br /> #include <lla/select_server/SelectServer.h><br /> #include <lla/select_server/Socket.h><br /> <br /> using lla::select_server::PipeSocket;<br /> <br /> int main() {<br /> // Create the select server<br /> lla::select_server::SelectServer ss;<br /> <br /> // Create the pipe socket to talk to the server on<br /> PipeSocket *pipe_socket = new PipeSocket();<br /> if (!pipe_socket->Init())<br /> return -1;<br /> <br /> // Remember to add this socket to the SelectServer<br /> ss.AddSocket(pipe_socket);<br /> <br /> // Setup the LlaClient<br /> lla::LlaClient client(pipe_socket);<br /> if (!client.Setup())<br /> return -1;<br /> <br /> // At this point the client is setup. We then need to setup the LLAServer<br /> // ...<br /> <br /> // Once that is done we add the pipe as a new connection<br /> lla_server->NewConnection(m_pipe_socket->OppositeEnd());<br /> }<br /> <br /> <br /> This example shows how we can create our own instance of a ''ConnectedSocket'' (''PipeSocket'' is a subclass of ''ConnectedSocket'') and pass it to the ''LlaClient'' to use. This code is very similar to what ''SimpleClient'' does under the hood.</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_Client_API&diff=2682 OLA Client API 2009-02-17T23:45:44Z

<p>216.239.45.4: /* Example IV: More complex client */</p> <hr /> <div>'''Note:''' This refers to the most recent version of LLA [>= 0.3.0]<br /> <br /> LLA provides a client library which allows other applications to send/receive DMX as well as control the LLA server. To cater for different application requirements, helper classes as provided which can be used to do most of the client setup / management. <br /> <br /> <br /> ==Example I: Sending an DMX update==<br /> <br /> This first client simply connects to the LLA Server and sends one DMX update. It's about as simple as you can get because it requires no callbacks and exits immediately. We use two classes in this example, ''lla::SimpleClient'', and ''lla::LlaClient''.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> int main() {<br /> // some dummy dmx data<br /> dmx_t dmx_data[] = {0, 128, 255};<br /> <br /> lla::SimpleClient simple_client;<br /> if (!simple_client.Setup())<br /> //setup failed<br /> return -1;<br /> <br /> // Get the underlying LlaClient<br /> lla::LlaClient *client = simple_client.GetClient();<br /> <br /> // Send the DMX data <br /> client->SendDmx(1, dmx_data, sizeof(dmx_data));<br /> }<br /> <br /> <br /> The main class used to communicate with the LLA Server is ''LlaClient''. For ease of use, the ''SimpleClient'' class sets up ''LlaClient'' with a connection to an LLA Server running on the localhost:LLA_DEFAULT_PORT. You can call GetClient() on a ''SimpleClient'' instance to get a pointer to the underlying ''LlaClient''.<br /> <br /> <br /> ==Example II: Sending multiple updates==<br /> <br /> The previous example only sent a single DMX update before quitting. This next example adds a timeout which sends DMX every 50ms. This introduces a new class ''SelectServer'' which is used for registering timeouts.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> // Maximum value of a dmx channel<br /> static const unsigned int MAX_DMX = 255;<br /> // How often to send updates<br /> static const unsigned int TIMEOUT_MS = 50;<br /> <br /> class DmxTimeout: public lla::select_server::TimeoutListener {<br /> public:<br /> DmxTimeout(lla::LlaClient *client):<br /> TimeoutListener(), m_tick(0), m_client(client) {}<br /> <br /> // Called on timeout<br /> int Timeout() {<br /> m_dmx_data[0] = MAX_DMX;<br /> m_dmx_data[1] = m_tick;<br /> m_dmx_data[2] = MAX_DMX - m_tick;<br /> m_client->SendDmx(1, m_dmx_data, sizeof(m_dmx_data));<br /> m_tick++;<br /> m_tick %= MAX_DMX + 1;<br /> }<br /> private:<br /> unsigned int m_tick;<br /> dmx_t m_dmx_data[3];<br /> lla::LlaClient *m_client;<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::select_server::SelectServer *ss = simple_client.GetSelectServer();<br /> // Create a timeout and register it<br /> DmxTimeout timeout(simple_client.GetClient());<br /> ss->RegisterTimeout(TIMEOUT_MS, &timeout);<br /> <br /> // Start the main loop<br /> ss->Run();<br /> }<br /> <br /> <br /> In this example we create ''DmxTimeout'' class whose ''Timeout()'' method is called every time the timer expires. We use the ''Timeout()'' method to send DMX data.<br /> <br /> The other important part here is the ''SelectServer''. As well as the ''RegisterTimeout'' method we've used above, this can also be used to register sockets so we can respond to network activity. The ''Run()'' method starts the main event processing loop which will halt if an error occurs or ''Terminate()'' is called.<br /> <br /> ==Example III: Receiving DMX data==<br /> <br /> The third example shows how to listen and respond to event from the LLA server.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> static const unsigned int UNIVERSE = 1;<br /> <br /> class OurObserver: public lla::LlaClientObserver {<br /> public:<br /> // Called when new DMX values arrive<br /> void NewDmx(unsigned int universe, unsigned int length,<br /> dmx_t *data, const std::string &error) {<br /> printf("received %d channels for universe %d\n",<br /> length, universe);<br /> }<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> OurObserver observer;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::LlaClient *client = simple_client.GetClient();<br /> // Set the observer and register our interest in this universe<br /> client->SetObserver(&observer);<br /> client->RegisterUniverse(UNIVERSE, lla::REGISTER);<br /> simple_client.GetSelectServer()->Run();<br /> }<br /> <br /> <br /> Here we inherit from the ''LlaClientObserver'' class and override the methods we're interested in receiving notification for.<br /> <br /> In the main function we set the observer object and register our interest in a universe.<br /> <br /> ==Example IV: More complex client==<br /> <br /> The above is all well and good but what if the main application has it's own event processing loop? An example of this is a GTK/Glib application which uses GMainLoop.<br /> <br /> On the other hand, what if you're not connecting to the LLA Server over TCP? Sometimes it may be desirable to embed the LLA server within the main application.<br /> <br /> Bypassing the SimpleClient and using LlaClient directly addresses both these problems.<br /> <br /> <br /> #include <lla/LlaClient.h><br /> #include <lla/select_server/SelectServer.h><br /> #include <lla/select_server/Socket.h><br /> <br /> using lla::select_server::PipeSocket;<br /> <br /> int main() {<br /> // Create the select server<br /> lla::select_server::SelectServer ss;<br /> <br /> // Create the pipe socket to talk to the server on<br /> PipeSocket *pipe_socket = new PipeSocket();<br /> if (!pipe_socket->Init())<br /> return -1;<br /> <br /> // Remember to add this socket to the SelectServer<br /> ss.AddSocket(pipe_socket);<br /> <br /> // Setup the LlaClient<br /> lla::LlaClient client(pipe_socket);<br /> if (!client.Setup())<br /> return -1;<br /> <br /> // At this point the client is setup. We then need to setup the LLAServer<br /> // ...<br /> <br /> // Once that is done we add the pipe as a new connection<br /> lla_server->NewConnection(m_pipe_socket->OppositeEnd());<br /> }<br /> <br /> <br /> This example shows how we can create our own instance of a ''ConnectedSocket'' (''PipeSocket'' is a subclass of ''ConnectedSocket'') and pass it to the ''LlaClient'' to use. This code is very similar to what ''SimpleClient'' does under the hood.</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_Client_API&diff=2681 OLA Client API 2009-02-17T22:54:33Z

<p>216.239.45.4: </p> <hr /> <div>'''Note:''' This refers to the most recent version of LLA [>= 0.3.0]<br /> <br /> LLA provides a client library which allows other applications to send/receive DMX as well as control the LLA server. To cater for different application requirements, helper classes as provided which can be used to do most of the client setup / management. <br /> <br /> <br /> ==Example I: Sending an DMX update==<br /> <br /> This first client simply connects to the LLA Server and sends one DMX update. It's about as simple as you can get because it requires no callbacks and exits immediately. We use two classes in this example, ''lla::SimpleClient'', and ''lla::LlaClient''.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> int main() {<br /> // some dummy dmx data<br /> dmx_t dmx_data[] = {0, 128, 255};<br /> <br /> lla::SimpleClient simple_client;<br /> if (!simple_client.Setup())<br /> //setup failed<br /> return -1;<br /> <br /> // Get the underlying LlaClient<br /> lla::LlaClient *client = simple_client.GetClient();<br /> <br /> // Send the DMX data <br /> client->SendDmx(1, dmx_data, sizeof(dmx_data));<br /> }<br /> <br /> <br /> The main class used to communicate with the LLA Server is ''LlaClient''. For ease of use, the ''SimpleClient'' class sets up ''LlaClient'' with a connection to an LLA Server running on the localhost:LLA_DEFAULT_PORT. You can call GetClient() on a ''SimpleClient'' instance to get a pointer to the underlying ''LlaClient''.<br /> <br /> <br /> ==Example II: Sending multiple updates==<br /> <br /> The previous example only sent a single DMX update before quitting. This next example adds a timeout which sends DMX every 50ms. This introduces a new class ''SelectServer'' which is used for registering timeouts.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> // Maximum value of a dmx channel<br /> static const unsigned int MAX_DMX = 255;<br /> // How often to send updates<br /> static const unsigned int TIMEOUT_MS = 50;<br /> <br /> class DmxTimeout: public lla::select_server::TimeoutListener {<br /> public:<br /> DmxTimeout(lla::LlaClient *client):<br /> TimeoutListener(), m_tick(0), m_client(client) {}<br /> <br /> // Called on timeout<br /> int Timeout() {<br /> m_dmx_data[0] = MAX_DMX;<br /> m_dmx_data[1] = m_tick;<br /> m_dmx_data[2] = MAX_DMX - m_tick;<br /> m_client->SendDmx(1, m_dmx_data, sizeof(m_dmx_data));<br /> m_tick++;<br /> m_tick %= MAX_DMX + 1;<br /> }<br /> private:<br /> unsigned int m_tick;<br /> dmx_t m_dmx_data[3];<br /> lla::LlaClient *m_client;<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::select_server::SelectServer *ss = simple_client.GetSelectServer();<br /> // Create a timeout and register it<br /> DmxTimeout timeout(simple_client.GetClient());<br /> ss->RegisterTimeout(TIMEOUT_MS, &timeout);<br /> <br /> // Start the main loop<br /> ss->Run();<br /> }<br /> <br /> <br /> In this example we create ''DmxTimeout'' class whose ''Timeout()'' method is called every time the timer expires. We use the ''Timeout()'' method to send DMX data.<br /> <br /> The other important part here is the ''SelectServer''. As well as the ''RegisterTimeout'' method we've used above, this can also be used to register sockets so we can respond to network activity. The ''Run()'' method starts the main event processing loop which will halt if an error occurs or ''Terminate()'' is called.<br /> <br /> ==Example III: Receiving DMX data==<br /> <br /> The third example shows how to listen and respond to event from the LLA server.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> static const unsigned int UNIVERSE = 1;<br /> <br /> class OurObserver: public lla::LlaClientObserver {<br /> public:<br /> // Called when new DMX values arrive<br /> void NewDmx(unsigned int universe, unsigned int length,<br /> dmx_t *data, const std::string &error) {<br /> printf("received %d channels for universe %d\n",<br /> length, universe);<br /> }<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> OurObserver observer;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::LlaClient *client = simple_client.GetClient();<br /> // Set the observer and register our interest in this universe<br /> client->SetObserver(&observer);<br /> client->RegisterUniverse(UNIVERSE, lla::REGISTER);<br /> simple_client.GetSelectServer()->Run();<br /> }<br /> <br /> <br /> Here we inherit from the ''LlaClientObserver'' class and override the methods we're interested in receiving notification for.<br /> <br /> In the main function we set the observer object and register our interest in a universe.<br /> <br /> ==Example IV: More complex client==</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_Client_API&diff=2680 OLA Client API 2009-02-17T22:48:17Z

<p>216.239.45.4: /* Example III: Receiving DMX data */</p> <hr /> <div>LLA provides a client library which allows other applications to send/receive DMX as well as control the LLA server. To cater for different application requirements, helper classes as provided which can be used to do most of the client setup / management. <br /> <br /> <br /> ==Example I: Sending an DMX update==<br /> <br /> This first client simply connects to the LLA Server and sends one DMX update. It's about as simple as you can get because it requires no callbacks and exits immediately. We use two classes in this example, ''lla::SimpleClient'', and ''lla::LlaClient''.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> int main() {<br /> // some dummy dmx data<br /> dmx_t dmx_data[] = {0, 128, 255};<br /> <br /> lla::SimpleClient simple_client;<br /> if (!simple_client.Setup())<br /> //setup failed<br /> return -1;<br /> <br /> // Get the underlying LlaClient<br /> lla::LlaClient *client = simple_client.GetClient();<br /> <br /> // Send the DMX data <br /> client->SendDmx(1, dmx_data, sizeof(dmx_data));<br /> }<br /> <br /> <br /> The main class used to communicate with the LLA Server is ''LlaClient''. For ease of use, the ''SimpleClient'' class sets up ''LlaClient'' with a connection to an LLA Server running on the localhost:LLA_DEFAULT_PORT. You can call GetClient() on a ''SimpleClient'' instance to get a pointer to the underlying ''LlaClient''.<br /> <br /> <br /> ==Example II: Sending multiple updates==<br /> <br /> The previous example only sent a single DMX update before quitting. This next example adds a timeout which sends DMX every 50ms. This introduces a new class ''SelectServer'' which is used for registering timeouts.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> // Maximum value of a dmx channel<br /> static const unsigned int MAX_DMX = 255;<br /> // How often to send updates<br /> static const unsigned int TIMEOUT_MS = 50;<br /> <br /> class DmxTimeout: public lla::select_server::TimeoutListener {<br /> public:<br /> DmxTimeout(lla::LlaClient *client):<br /> TimeoutListener(), m_tick(0), m_client(client) {}<br /> <br /> // Called on timeout<br /> int Timeout() {<br /> m_dmx_data[0] = MAX_DMX;<br /> m_dmx_data[1] = m_tick;<br /> m_dmx_data[2] = MAX_DMX - m_tick;<br /> m_client->SendDmx(1, m_dmx_data, sizeof(m_dmx_data));<br /> m_tick++;<br /> m_tick %= MAX_DMX + 1;<br /> }<br /> private:<br /> unsigned int m_tick;<br /> dmx_t m_dmx_data[3];<br /> lla::LlaClient *m_client;<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::select_server::SelectServer *ss = simple_client.GetSelectServer();<br /> // Create a timeout and register it<br /> DmxTimeout timeout(simple_client.GetClient());<br /> ss->RegisterTimeout(TIMEOUT_MS, &timeout);<br /> <br /> // Start the main loop<br /> ss->Run();<br /> }<br /> <br /> <br /> In this example we create ''DmxTimeout'' class whose ''Timeout()'' method is called every time the timer expires. We use the ''Timeout()'' method to send DMX data.<br /> <br /> The other important part here is the ''SelectServer''. As well as the ''RegisterTimeout'' method we've used above, this can also be used to register sockets so we can respond to network activity. The ''Run()'' method starts the main event processing loop which will halt if an error occurs or ''Terminate()'' is called.<br /> <br /> ==Example III: Receiving DMX data==<br /> <br /> The third example shows how to listen and respond to event from the LLA server.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> static const unsigned int UNIVERSE = 1;<br /> <br /> class OurObserver: public lla::LlaClientObserver {<br /> public:<br /> // Called when new DMX values arrive<br /> void NewDmx(unsigned int universe, unsigned int length,<br /> dmx_t *data, const std::string &error) {<br /> printf("received %d channels for universe %d\n",<br /> length, universe);<br /> }<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> OurObserver observer;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::LlaClient *client = simple_client.GetClient();<br /> // Set the observer and register our interest in this universe<br /> client->SetObserver(&observer);<br /> client->RegisterUniverse(UNIVERSE, lla::REGISTER);<br /> simple_client.GetSelectServer()->Run();<br /> }<br /> <br /> <br /> Here we inherit from the ''LlaClientObserver'' class and override the methods we're interested in receiving notification for.<br /> <br /> In the main function we set the observer object and register our interest in a universe.<br /> <br /> ==Example IV: More complex client==</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_Client_API&diff=2679 OLA Client API 2009-02-17T22:33:48Z

<p>216.239.45.4: </p> <hr /> <div>LLA provides a client library which allows other applications to send/receive DMX as well as control the LLA server. To cater for different application requirements, helper classes as provided which can be used to do most of the client setup / management. <br /> <br /> <br /> ==Example I: Sending an DMX update==<br /> <br /> This first client simply connects to the LLA Server and sends one DMX update. It's about as simple as you can get because it requires no callbacks and exits immediately. We use two classes in this example, ''lla::SimpleClient'', and ''lla::LlaClient''.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> int main() {<br /> // some dummy dmx data<br /> dmx_t dmx_data[] = {0, 128, 255};<br /> <br /> lla::SimpleClient simple_client;<br /> if (!simple_client.Setup())<br /> //setup failed<br /> return -1;<br /> <br /> // Get the underlying LlaClient<br /> lla::LlaClient *client = simple_client.GetClient();<br /> <br /> // Send the DMX data <br /> client->SendDmx(1, dmx_data, sizeof(dmx_data));<br /> }<br /> <br /> <br /> The main class used to communicate with the LLA Server is ''LlaClient''. For ease of use, the ''SimpleClient'' class sets up ''LlaClient'' with a connection to an LLA Server running on the localhost:LLA_DEFAULT_PORT. You can call GetClient() on a ''SimpleClient'' instance to get a pointer to the underlying ''LlaClient''.<br /> <br /> <br /> ==Example II: Sending multiple updates==<br /> <br /> The previous example only sent a single DMX update before quitting. This next example adds a timeout which sends DMX every 50ms. This introduces a new class ''SelectServer'' which is used for registering timeouts.<br /> <br /> #include <lla/SimpleClient.h><br /> <br /> // Maximum value of a dmx channel<br /> static const unsigned int MAX_DMX = 255;<br /> // How often to send updates<br /> static const unsigned int TIMEOUT_MS = 50;<br /> <br /> class DmxTimeout: public lla::select_server::TimeoutListener {<br /> public:<br /> DmxTimeout(lla::LlaClient *client):<br /> TimeoutListener(), m_tick(0), m_client(client) {}<br /> <br /> // Called on timeout<br /> int Timeout() {<br /> m_dmx_data[0] = MAX_DMX;<br /> m_dmx_data[1] = m_tick;<br /> m_dmx_data[2] = MAX_DMX - m_tick;<br /> m_client->SendDmx(1, m_dmx_data, sizeof(m_dmx_data));<br /> m_tick++;<br /> m_tick %= MAX_DMX + 1;<br /> }<br /> private:<br /> unsigned int m_tick;<br /> dmx_t m_dmx_data[3];<br /> lla::LlaClient *m_client;<br /> };<br /> <br /> int main() {<br /> lla::SimpleClient simple_client;<br /> <br /> if (!simple_client.Setup())<br /> return -1;<br /> <br /> lla::select_server::SelectServer *ss = simple_client.GetSelectServer();<br /> // Create a timeout and register it<br /> DmxTimeout timeout(simple_client.GetClient());<br /> ss->RegisterTimeout(TIMEOUT_MS, &timeout);<br /> <br /> // Start the main loop<br /> ss->Run();<br /> }<br /> <br /> <br /> In this example we create ''DmxTimeout'' class whose ''Timeout()'' method is called every time the timer expires. We use the ''Timeout()'' method to send DMX data.<br /> <br /> The other important part here is the ''SelectServer''. As well as the ''RegisterTimeout'' method we've used above, this can also be used to register sockets so we can respond to network activity. The ''Run()'' method starts the main event processing loop which will halt if an error occurs or ''Terminate()'' is called.<br /> <br /> ==Example III: Receiving DMX data==<br /> <br /> ==Example IV: More complex client==</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_Linux&diff=2653 OLA on Linux 2009-02-07T02:10:22Z

<p>216.239.45.4: /* Configure */</p> <hr /> <div>=Installing LLA on Debian From GIT/Archive=<br /> <br /> This describes how to get LLA working on a Debian system. It should be pretty similar for any other Linux based OS.<br /> <br /> <br /> ==Checkout or Download an Archive==<br /> <br /> git clone xxxx<br /> <br /> ==Install libraries==<br /> <br /> You need a couple of libraries installed for everything to work correctly. Some of these are available as Debian packages but others need to be downloaded.<br /> <br /> First up we'll need microhttpd for the embedded web server (Note: if you want the dmx console to work you need the latest svn version):<br /> <br /> With apt:<br /> <br /> apt-get install libmicrohttpd-dev libmicrohttpd4 libcppunit-dev libcppunit-1.12-1<br /> <br /> From source or debian packages:<br /> <br /> libprotobuf2, libprotobuf-dev, protobuf-compiler<br /> [http://code.google.com/p/protobuf/ ProtocolBuffers]<br /> <br /> From source:<br /> <br /> [http://code.google.com/p/google-ctemplate/ CTemplate]<br /> <br /> Finally run ldconfig as root to pick up the new libraries<br /> <br /> ldconfig<br /> <br /> <br /> ==Configure==<br /> <br /> If you checked out the sources from git, you'll need to run<br /> <br /> autoreconf -i<br /> <br /> After that run<br /> <br /> ./configure<br /> <br /> ==Building & Testing==<br /> <br /> Build<br /> make<br /> <br /> Run the tests<br /> make check<br /> <br /> And install LLA<br /> sudo make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_OS_X&diff=2652 OLA on OS X 2009-02-07T02:06:49Z

<p>216.239.45.4: /* Run autoreconf */</p> <hr /> <div>This page describes how to get LLA 0.3 working on OS X. <br /> <br /> == Basic setup ==<br /> <br /> * Install xcode<br /> * install git<br /> * install mac ports [[http://www.macports.org/]]<br /> <br /> == Use Mac Ports to install stuff==<br /> <br /> $ port install pkgconfig protobuf-cpp cppunit unittest-cpp<br /> <br /> == Set some env vars==<br /> <br /> set $PATH to point to something sane<br /> <br /> export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig<br /> export CPPFLAGS="-I/opt/local/var/macports/software/protobuf-cpp/2.0.2_0/opt/local/include/"<br /> export LDFLAGS="-L/opt/local/var/macports/software/protobuf-cpp/2.0.2_0/opt/local/lib/"<br /> <br /> <br /> == Optionally install microhttpd and ctemplate==<br /> <br /> If you want the http interface you need these<br /> <br /> * http://www.gnu.org/software/libmicrohttpd/<br /> * http://code.google.com/p/google-ctemplate/<br /> <br /> == Run autoreconf==<br /> <br /> If this is the first time run with -i to install the missing files<br /> <br /> autoconf -i<br /> <br /> == Do the usual steps==<br /> <br /> ./configure<br /> make<br /> make check<br /> sudo make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_Linux&diff=2643 OLA on Linux 2009-01-20T04:51:39Z

<p>216.239.45.4: </p> <hr /> <div>=Installing LLA on Debian From GIT/Archive=<br /> <br /> This describes how to get LLA working on a Debian system. It should be pretty similar for any other Linux based OS.<br /> <br /> <br /> ==Checkout or Download an Archive==<br /> <br /> git clone xxxx<br /> <br /> ==Install libraries==<br /> <br /> You need a couple of libraries installed for everything to work correctly. Some of these are available as Debian packages but others need to be downloaded.<br /> <br /> First up we'll need microhttpd for the embedded web server:<br /> <br /> With apt:<br /> <br /> apt-get install libmicrohttpd-dev libmicrohttpd4 libcppunit-dev libcppunit-1.12-1<br /> <br /> From source or debian packages:<br /> <br /> libprotobuf2, libprotobuf-dev, protobuf-compiler<br /> [http://code.google.com/p/protobuf/ ProtocolBuffers]<br /> <br /> From source:<br /> <br /> [http://code.google.com/p/google-ctemplate/ CTemplate]<br /> <br /> Finally run ldconfig as root to pick up the new libraries<br /> <br /> ldconfig<br /> <br /> <br /> ==Configure==<br /> <br /> If you checked out the sources from git, you'll need to run<br /> <br /> autoreconf<br /> <br /> After that run<br /> <br /> ./configure<br /> <br /> ==Building & Testing==<br /> <br /> Build<br /> make<br /> <br /> Run the tests<br /> make check<br /> <br /> And install LLA<br /> sudo make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_Linux&diff=2642 OLA on Linux 2009-01-19T17:32:04Z

<p>216.239.45.4: </p> <hr /> <div>=Installing LLA on Debian From GIT/Archive=<br /> <br /> This describes how to get LLA working on a Debian system. It should be pretty similar for any other Linux based OS.<br /> <br /> <br /> ==Checkout or Download an Archive==<br /> <br /> git clone xxxx<br /> <br /> ==Install libraries==<br /> <br /> You need a couple of libraries installed for everything to work correctly. Some of these are available as Debian packages but others need to be downloaded.<br /> <br /> First up we'll need microhttpd for the embedded web server:<br /> <br /> With apt:<br /> <br /> apt-get install libmicrohttpd-dev libmicrohttpd4 libcppunit-dev libcppunit-1.12-1<br /> <br /> From source or debian packages:<br /> <br /> libprotobuf2, libprotobuf-dev, protobuf-compiler<br /> [http://code.google.com/p/protobuf/ ProtocolBuffers]<br /> <br /> From source:<br /> <br /> [http://code.google.com/p/google-ctemplate/ CTemplate]<br /> <br /> ==Configure==<br /> <br /> If you checked out the sources from git, you'll need to run<br /> <br /> autoreconf<br /> <br /> After that run<br /> <br /> ./configure<br /> <br /> ==Building & Testing==<br /> <br /> Build<br /> make<br /> <br /> Run the tests<br /> make check<br /> <br /> And install LLA<br /> sudo make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_on_Linux&diff=2641 OLA on Linux 2009-01-19T17:31:11Z

<p>216.239.45.4: New page: =Installing LLA on Debian From GIT/Archive= This describes how to get LLA working on a Debian system. It should be pretty similar for any other Linux based OS. ==Checkout or Download an...</p> <hr /> <div>=Installing LLA on Debian From GIT/Archive=<br /> <br /> This describes how to get LLA working on a Debian system. It should be pretty similar for any other Linux based OS.<br /> <br /> <br /> ==Checkout or Download an Archive==<br /> <br /> git clone xxxx<br /> <br /> ==Install libraries==<br /> <br /> You need a couple of libraries installed for everything to work correctly. Some of these are available as Debian packages but others need to be downloaded.<br /> <br /> First up we'll need microhttpd for the embedded web server:<br /> <br /> With apt:<br /> <br /> apt-get install libmicrohttpd-dev libmicrohttpd4<br /> <br /> From source or debian packages:<br /> <br /> libprotobuf2, libprotobuf-dev, protobuf-compiler<br /> [http://code.google.com/p/protobuf/ ProtocolBuffers]<br /> <br /> From source:<br /> <br /> [http://code.google.com/p/google-ctemplate/ CTemplate]<br /> <br /> ==Configure==<br /> <br /> If you checked out the sources from git, you'll need to run<br /> <br /> autoreconf<br /> <br /> After that run<br /> <br /> ./configure<br /> <br /> ==Building & Testing==<br /> <br /> Build<br /> make<br /> <br /> Run the tests<br /> make check<br /> <br /> And install LLA<br /> sudo make install</div>

216.239.45.4 https://wiki.openlighting.org/index.php?title=OLA_0.3&diff=2640 OLA 0.3 2009-01-18T18:49:52Z

<p>216.239.45.4: </p> <hr /> <div>This page discusses the development release of LLA (0.3).<br /> <br /> ==User facing changes==<br /> <br /> * (Optional) HTTP server with web interface for configuration<br /> * Support for embedding<br /> * OS X support<br /> <br /> <br /> ==Internal changes==<br /> <br /> * Completely new RPC system based on [[http://code.google.com/p/protobuf/ Protocol Buffers]]<br /> * ExportMap<br /> <br /> ==Still left to complete==<br /> <br /> * convert all the plugins to the new format<br /> * convert the usb_pro binary to the new format<br /> * check everything works under Linux correctly<br /> <br /> <br /> ==Other Docs==<br /> <br /> * [[LLA on OS X]]<br /> * [[LLA on Debian]]</div>

216.239.45.4