 | | finally works
|
|
finally works.... the problem was in the Makefile.common file, finally change the line: # LEGOS_ROOT=$(HOME)/legOS/ with: LEGOS_ROOT=/legOS-0.2.6/ thanks a lot for your posts!! :-) (22 years ago, 8-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS library path
|
|
(...) Ok. So for cygwin, the path is /legos-0.2.6 (...) Is that right? I think it must read c:\cygwin\legos-0.2.6\mycode. (...) Ok. (...) That is ok. (...) First the good news: Makefile.common and Makefile.user are correctly included. Otherwise, the (...) (22 years ago, 7-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS library path
|
|
(...) To make it so that your code can live anywhere (i.e., not necessarily beneath the cygwin and/or BrickOS root directory you should make the following changes to your Makefile. 1. replace any relative paths (i.e., ../ or ../../ etc.) with (...) (22 years ago, 8-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS library path
|
|
"Germán Rojas" <ge-rojas@uniandes.edu.co> wrote in message news:H3MD68.M72@lugnet.com... (...) Hi there! (...) [snip] (...) [snip] (...) [snip] This broke for me between legOS 0.2.5 and 0.2.6 I belive (and is still broken in the current brickos (...) (22 years ago, 8-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS library path
|
|
"Germán Rojas" <ge-rojas@uniandes.edu.co> wrote in message news:H3Mp27.CBz@lugnet.com... (...) <snip> (...) <snip> You should add 'mycode' to the list of directories found in Makefile, just after demo. Then always run make from the legOS root (...) (22 years ago, 7-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS library path
|
|
I install legOS in the follow directory: C:\cygwin\legos-0.2.6 (the same like the windows instructions) Create the follow directory: C:\legos-0.2.6\mycode Copy the *.c and Makefile files in C:\legos-0.2.6\mycode In the Makefile default file i think (...) (22 years ago, 7-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS library path
|
|
(...) You have to look where you are and where the makefile searches for other needed files. In the moment, you makefile hopes to find the include files under /legos/include. Is that ok? If you installed legos into your home directory, the path must (...) (22 years ago, 7-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | legOS library path
|
|
Hello!! Testing the instalation of legOS-0.2.6 (cygwin) after download succesfully the firmware and some sample programs of demo directory to the RCX, i create a new directory called mycode, i put all the *.c and Makefile files from demo directory, (...) (22 years ago, 7-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Remotely starting RCX
|
|
Thanks!!! (...) (22 years ago, 5-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS & BricxCC - coming soon to a Windows PC near you
|
|
(...) You manage your projects now, I'm guessing, simply by directory structure and the contents of your make file? Do you put targets in your make file which execute dll to download the .lx to the brick or do you usually perform that step as a (...) (22 years ago, 5-Oct-02, to lugnet.robotics.rcx.legos)
|
