{"id":1611,"date":"2016-05-13T13:20:48","date_gmt":"2016-05-13T20:20:48","guid":{"rendered":"http:\/\/internetofhomethings.com\/homethings\/?p=1611"},"modified":"2016-05-13T13:20:48","modified_gmt":"2016-05-13T20:20:48","slug":"usb-lamp-web-server-part-6-code-compiler","status":"publish","type":"post","link":"https:\/\/internetofhomethings.com\/homethings\/?p=1611","title":{"rendered":"USB LAMP Web Server Part 6 – Code Compiler"},"content":{"rendered":"

<\/a><\/p>\n

All Under One Roof<\/strong><\/h2>\n

The LAMP server in this series has been built using the Precise Puppy Linux Distribution. But in my case, I had experimented with several different distributions. And my development environment for compiling \u00a0code was on a different distribution of Linux than the LAMP. In addition,\u00a0the main application in this other Linux distribution, an MQTT Broker, is\u00a0needed often for IoT setups.<\/p>\n

This became very messy. Swapping out the USB sticks for different projects. The solution is obvious. Consolidate the development environment and the MQTT Broker into the USB LAMP Server.<\/p>\n

One USB stick for everything…<\/p>\n

Web Server, mySQL, WordPress, MQTT Broker, and other application that needs to be compiled.<\/p>\n

These\u00a0added capabilities\u00a0have been broken down into two parts:<\/p>\n

USB LAMP Web Server Part 6 – \u00a0Code Compiler<\/p>\n

USB LAMP Web Server Part 7\u00a0– \u00a0MQTT Broker<\/p>\n

Adding the Code Compiler<\/strong><\/h2>\n

First thing to do is to get the Linux development tools for the Precise Puppy Distribution. They are bundled in the file “devx_precise_5.7.sfs”, which you can download\u00a0here<\/a>.<\/p>\n

Copy this file to the USB LAMP drive root directory (from a Windows OS computer).<\/p>\n

Now let’s configure the USB LAMP to startup with the development tools. Here is how to do it…<\/p>\n

Start the USB LAMP.<\/p>\n

First, click on the menu in the lower left hand of the start-up screen, selecting:<\/p>\n

Menu>System>BootManager configure bootup<\/p>\n

Click on the icon to the right of “Choose which extra SFS files to load at bootup:”<\/p>\n

Select “devx_precise_5.7.sfs” and click “OK”.<\/p>\n

Now close all the open windows and reboot Linux from the menu.<\/p>\n

Menu>Exit>Reboot<\/p>\n

That’s it!<\/p>\n

Everything you need to create and execute programs are now installed. To test this setup, let’s code and run the classic “Hello World!” program…<\/p>\n

Let’s keep things tidy by creating a folder for programs we create. And to keep things visible when we use the USB stick with the Windows OS running, the folder needs to be located under the “Home” folder. That is the Linux folder that appears as the “root” folder under the drive letter assigned by Windows.<\/p>\n

To navigate to the Home folder using the Puppy GUI, first click on the “file” icon from the startup screen.<\/p>\n

\"compiler_file\"<\/a><\/p>\n

Click on the left “up arrow” icon to get to the parent folder.<\/p>\n

\"parent-folder\"<\/a><\/p>\n

Then select the “mnt” folder.<\/p>\n

\"folder-mnt-sel\"<\/a><\/p>\n

And finally, the “Home” folder.<\/p>\n

\"home\"<\/a><\/p>\n

To create a folder, right-click the mouse in the home folder list of files and select:<\/p>\n

New>Directory<\/p>\n

\"folder-create\"<\/a><\/p>\n

Change “NewDir” to “MyPrograms” and click on the “Create” button.<\/p>\n

\"folder-create-MyPrograms\"<\/a><\/p>\n

Now click on the “MyPrograms” folder. We shall now create one additional folder under this one for our first program. Just like before,\u00a0to create a folder, right-click the mouse in the MyPrograms folder list of files and select:<\/p>\n

New>Directory<\/p>\n

Change “NewDir” to “HelloWorld” and click on the “Create” button.<\/p>\n

Now click on the “HelloWorld” folder. This time,\u00a0to create our source code file, right-click the mouse in the HelloWorld folder list of files and select:<\/p>\n

New>Blank file<\/p>\n

\"folder-MyPrograms-Blank\"<\/a><\/p>\n

Change “NewFile” to “HelloWorld.c” and click on the “Create” button.<\/p>\n

Click on the file listed as “HelloWorld.c” to open the file editor.<\/p>\n

\"select-helloworld-file\"<\/a><\/p>\n

For the minimal first program, enter the following:<\/p>\n

\"save-helloworld\"<\/a><\/p>\n

Click on the “save” icon to finish the creation of this file.<\/p>\n

Now we need a “Makefile” to define how to compile and build the program. This will be a minimal Makefile for this first program. Just like the “c” file, create a file named “Makefile” and enter the following contents:<\/p>\n

\"makefile\"<\/a><\/p>\n

Got it?<\/p>\n

Now we are ready to build and execute the program. This can be done two different ways.<\/p>\n

    \n
  1. Using the GUI editor we currently have open.<\/li>\n
  2. From the command line.<\/li>\n<\/ol>\n

    Since the GUI file editor is already open, let’s first build and run the program from that environment. This is really easy. Like 1-2-3…<\/p>\n

    Build and Execute Using the GUI<\/strong><\/h2>\n

    Step 1: Select the “HelloWord.c” source code file tab.
    \nStep 2: Click on the “Build” icon.<\/p>\n

    \"build-helloworld\"<\/a>
    \nStep 3: Click on the “Execute” icon.<\/p>\n

    \"execute-helloworld\"<\/a><\/p>\n

    Our one-line “prinf” command correctly displays on the console when the program is executed.<\/p>\n

    That’s great for a quick compile and run. But what I found is that if your program contains errors, nothing is displayed indicating what went wrong. Fortunately, there is a way to get needed error messages, when they occur.\u00a0\u00a0It requires you to use the command line to build and execute.<\/p>\n

    Fear not! It really is not that difficult…<\/p>\n

    Build and Execute Using the\u00a0Command Line<\/strong><\/h2>\n

    Now let’s do the same thing from the command line. To open a command line window, click on the “console” icon.<\/p>\n

    \"compiler_console\"<\/a><\/p>\n

    Then switch to the HelloWorld Folder:<\/p>\n

    \"change-dir-hello\"<\/a><\/p>\n

    You can view a directory listing now to verify the source and “Makefile” files are present with the “ls” command.<\/p>\n

    \"dir-listing\"<\/a><\/p>\n

    Now we can build the program with the command “gcc -o HelloWorld HelloWorld.c”. And run the program with the “.\/HelloWorld” command.<\/p>\n

    \"cmd-line-demo\"<\/a><\/p>\n

    That’s it. You are now setup to build and execute programs built for Linux.<\/p>\n

    Now\u00a0let’s see what happens if we put an error into the program. Enter a bogus line after the printf statement. Like “junk;”, for example. When we try to “make” this program with the error injected, an error is returned. Unlike the GUI, with no error information provided, this provides you with an indication of what went wrong.<\/p>\n

    So you can quickly correct the error.<\/p>\n

    \"error\"<\/a><\/p>\n

    Conclusions<\/strong><\/h2>\n

    Here you have a simple reference to use to setup a Linux development environment. It is another tool to add to your “bag of tricks”. You never know when it will be needed. Like when\u00a0the only solution available must be run using Linux.<\/p>\n

    Now that we have the development environment setup, we are set to\u00a0build and configure an MQTT Broker on our USB LAMP. That will be the topic covered in my next post.<\/p>\n

    Hope you find this information useful.<\/p>\n","protected":false},"excerpt":{"rendered":"

    All Under One Roof The LAMP server in this series has been built using the Precise Puppy Linux Distribution. But in my case, I had experimented with several different distributions. …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,19,111,132],"tags":[133,134],"class_list":["post-1611","post","type-post","status-publish","format-standard","hentry","category-alltheposts","category-internet-of-things","category-mqtt","category-web-server","tag-lamp-server","tag-lamp-server-compiler"],"_links":{"self":[{"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=\/wp\/v2\/posts\/1611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1611"}],"version-history":[{"count":11,"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=\/wp\/v2\/posts\/1611\/revisions"}],"predecessor-version":[{"id":1631,"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=\/wp\/v2\/posts\/1611\/revisions\/1631"}],"wp:attachment":[{"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1611"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1611"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/internetofhomethings.com\/homethings\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}