 | | Cygwin/Gcc/Legos-0.2.6 Installation
|
|
Hello, I finally got make to complete without any apparent errors. At the end of the process, no errors were shown. I had to move the proper copy of objcopy.exe to the required directory and I also had to copy the proper copy of g++.exe to the same (...) (22 years ago, 10-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Gcc Problems
|
|
Rick, It sounds as if you have gcc working, however, the version of objcopy that you copied from another folder is incompatible with the hitachi h8 version of gcc. You need to have a special version of objcopy that is designed for the h8 (the RCX). (...) (22 years ago, 9-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Gcc Problems
|
|
Hello, There is a line under Hitachi H8 tool prefix that goes like this: HMSTOOLDIR=/usr/local/crossgcc. I changed it to HMSTOOLDIR=/usr/local and I changed TOOLPREFIX=$(HMSTOOL...tachi-hms- to TOOLPREFIX=$(HMSTOOL...i-hms/bin. After looking through (...) (22 years ago, 9-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Gcc Problems
|
|
Some versions of the gcc executables are named h8300-hms-*.exe (ex: h8300-hms-gcc.exe) The Makefile.common, as you pointed out expects h8300-hitachi-hms-*.exe If this is what you are experiencing, then you have two options: 1) make copies of them, (...) (22 years ago, 9-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Gcc Problems
|
|
(...) Your previous post indicated that you were running under cygwin, iirc, so the line to which you refer above is not where your problem lies. In Makefile.common there are several sections that only apply to a particular operating system, cygwin, (...) (22 years ago, 9-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Gcc Problems
|
|
Hello, I looked at the Makefile.common file and there is a line that goes as follows: TOOLPREFIX=$(HMSTOOL...tachi-hms- Could this be where my problem lies according to what I said in the previous post earlier today? Thanks Much, Rick Bonari (22 years ago, 9-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Cygwin/Gcc/Legos Installation
|
|
Hello, Need some help on deciphering the following Errors: Errors when executing the Make Depend Command: ...../h8300-hitachi-hms-gcc: not found make [1]: ***[depend] Error 127 make: ***[depend] Error 2 Errors when executing the Make Command: (...) (22 years ago, 9-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | 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)
|
| |
| | Re: not found
|
|
Shehryar Shaheen <shehryar.shaheen@ul.ie> wrote in message news:000901c26bd4$fe...SHAHEEN... (...) You should find this utility in the fileutils package. Ed (22 years ago, 5-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS & BricxCC - coming soon to a Windows PC near you
|
|
Hello John, (...) That would be real real great! (...) That should work. At my system, bigger projects are broken into several source files. It is easier for me to work with them then with a huge single source file. (...) Why not? BrickOS can handle (...) (22 years ago, 5-Oct-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Remotely starting RCX
|
|
Hello Henk, (...) If you run "dll" without a file name to download, dll will tell you all it's switches. One is the -e switch, that executes the program you download. So "dll -e helloworld.lx" will download helloworld and run it. Another possible (...) (22 years ago, 5-Oct-02, to lugnet.robotics.rcx.legos)
|
