It's an error in the Makefile. Usually caused by not using tabs but spaces.zack-qeng wrote:C:\BricxCC\API\button_test_c.mak:23: *** missing separator. Stop.
Search found 23 matches
- 19 Jun 2014, 11:39
- Forum: Mindstorms Software
- Topic: Odd Compiler Error
- Replies: 1
- Views: 6455
Re: Odd Compiler Error
- 24 Feb 2014, 23:53
- Forum: Mindstorms Software
- Topic: Bounty for complete EV3 C/C++ API
- Replies: 60
- Views: 263127
Re: Bounty for complete EV3 C/C++ API
No, I don't want to compete wih you.doc-helmut wrote:So I don't see your point, or are you just trolling again?
- 24 Feb 2014, 19:43
- Forum: Mindstorms Software
- Topic: hw brickbench: Benchmark test for NXT and EV3
- Replies: 36
- Views: 149385
Re: hw brickbench: Benchmark test for NXT and EV3
No I did want to help you with your sorting experience. Sorry for that, will not try such again.
- 24 Feb 2014, 19:41
- Forum: Mindstorms Software
- Topic: Bounty for complete EV3 C/C++ API
- Replies: 60
- Views: 263127
Re: Bounty for complete EV3 C/C++ API
3. Just writing an API doesn't work as you have to change the existing firmware a lot . that's a surprising standpoint - no one ever mentioned or suspected that there would be any need to do this . It isn't if you still want to be compatible with lms (that means if you still want to use EV3-G too, ...
- 24 Feb 2014, 18:25
- Forum: Mindstorms Software
- Topic: hw brickbench: Benchmark test for NXT and EV3
- Replies: 36
- Views: 149385
Re: hw brickbench: Benchmark test for NXT and EV3
Which hardware of software platform is of your interest? Sorry, I have no interest at all. I just wondered about that header and would suggest the use of one of the proved open source licences like BSD, (L)GPL or one of those Creative Commons licences. That would save a lot of time and questions as...
- 24 Feb 2014, 12:30
- Forum: Mindstorms Software
- Topic: Bounty for complete EV3 C/C++ API
- Replies: 60
- Views: 263127
Re: Bounty for complete EV3 C/C++ API
In regard to the topic of this thread, I only can support Xander. It's an unrealistic thread and should die. Nobody sane would consider to go for that bounty: 1. It's highly unlikely to be able to collect the mentioned money 2. The amount of money doesn't make sense compared with the amount of neces...
- 23 Feb 2014, 20:22
- Forum: Mindstorms Software
- Topic: hw brickbench: Benchmark test for NXT and EV3
- Replies: 36
- Views: 149385
Re: hw brickbench: Benchmark test for NXT and EV3
Meanwhile also the RobotC benchmark is finished, and there were surprises in many ways: 1st, the sort algorithm (Shellsort) has by far the worst performance of all tests and ruins the overall benchmark; a faster sort algorithm surely would be appreciated. Furthermore, most basic calculations are so...
- 23 Feb 2014, 19:49
- Forum: Mindstorms Software
- Topic: Bounty for complete EV3 C/C++ API
- Replies: 60
- Views: 263127
Re: Bounty for complete EV3 C/C++ API
If single shot mode is a mode that can be set like other sensor modes, then setSensorMode(port, mode) should work, if you know the mode number... otherwise I'm not sure. Sending single I2C commands on the EV3 is broken. The (ev3-linux-i2c-)driver has a bug there which repeats I2C commands even if i...
- 01 Nov 2013, 20:50
- Forum: Mindstorms Hardware
- Topic: Looking for EV3 Infra Red Sensor and Beacon Specs
- Replies: 16
- Views: 42517
Re: Looking for EV3 Infra Red Sensor and Beacon Specs
The signal key on the EV3 IR remote sends a PF combo PWM command (Float) whereas the other keys do send PF combo direct commands. That's at least what I've used with the IRLink to send EV3 IR signals. The description of the "LEGO Power Functions RC" protocol describes the encoding of those...
- 25 Oct 2013, 20:40
- Forum: Mindstorms Software
- Topic: EV3 BCC / Sharing variables between threads
- Replies: 2
- Views: 10489
EV3 BCC / Sharing variables between threads
As this thread turned into some talk about multi-threading using C/C++, I think I should make people aware of another problem: sharing variables between threads. double d; void thread_1(void) { ... d+=10; } void thread_2(void) { double my_d = d; ... } A double is 64bits long on ARM, so the cpu needs...