TOSSIM Python compiling problem

When you use TOSSIM in TinyOS, you come up to this error:

In function ‘void SWIG_Python_FixMethods(PyMethodDef*, swig_const_info*, swig_type_info**, swig_type_info**)’
error: invalid conversion from ‘const char*’ to ‘char*’

(overall there are two errors like this one)

First check whether the error can be solved using solution on TinyOS wiki website on
TOSSIM .

If even than, it doesn't work,
go to $TOSROOT/tos/lib/tossim and run ./generate-swig.bash
In my case, it shows you some warnings, but that is ok.
afterwards, it worked fine for me.

If you still have troubles, check also:
python and python-dev should be on the same version,
swig should be installed.

If all this didnt solve your problems, good luck finding it, and I hope you put the solution somewhere on internet as well.

Comments

renesto said…
Take a look also on which version is written in sim.extra
Sometimes, for some other app requirements, you have updated the version of Python. Most likely, everything is already set, just a small thing called PYTHON_VERSION should be the right value.
April 28, 2011 at 1:17 PM
ivy said…
This comment has been removed by a blog administrator.
April 5, 2012 at 11:12 PM
Post a Comment

Popular posts from this blog

Exporting Skype Chat/Skype Contacts to csv file using the shell script and sqlite3 (usually already installed on mac)

Edit: a very first draft version of Skype Exporter have been made and released. https://github.com/renesto/SkypeExportSwift/releases check it, and report any issues to renesto-at-gmail.com I heard there are not so many nice ways to get the chat history from skype, so I came across a page of one guy who shows a way to open the sql chat history database and delete all conversations. I thought to make something more from that idea (as delete chat history is now one of the options in skype) Create a file exportFromSkype.sh place either this text: sqlite3 -batch "$HOME/Library/Application Support/Skype/$1/main.db" < <EOF .mode csv .output $2.csv select * from Messages where dialog_partner = '$2'; .output stdout .exit EOF now make the script executable by running chmod +x exportFromSkype.sh now, when you want to export some chat history from certain person, you can do it by: sh exportFromSkype.sh your_skype_name your_friends_skype_name and i...
Read more

trim() not supported by IE7 and IE8

Funny fact, trim function is not supported by IE7 and IE8. Ok, it is supported, but through jQuery trim function. So, when you have something like this: jQuery(...).attr().trim() , this trim() function stops having any relation to jQuery, as the attr() would return String type, which method would be then trim(). Since IE7 and IE8 do not support trim() method within String type, you should use instead jQuery.trim(jQuery(...).attr()) or if you don't wanna use jQuery (whyyyy?), you can simply implement the trim function youself. if(typeof String.prototype.trim !== 'function') { String.prototype.trim = function() { return this.replace(/^\s+|\s+$/g, ''); } } http://www.blogger.com/img/blank.gif source 1 source 2
Read more

Finally, clear explanation of TinyOS 2.x serial packet structure

Image
TinyOS 2.x A message sent through serial ports from motes to PC will typically look like this: 00 FF FF 00 00 08 00 09 19 77 02 07 00 13 00 00 The first byte 00 is the leading zero. After that, the whole packet is of the type " serial_packet_t ", defined in tinyos-2.x/tos/lib/serial/Serial.h . Inside the serial_packet_t structure, the first 7 bytes are of the type " serial_header_t" , which is also defined in tinyos-2.x/tos/lib/serial/Serial.h . In the case above, it would be FF FF 00 00 08 00 09 . Within the "serial_header_t", the following structure takes place: nx_am_addr_t dest // Destination (2 bytes) nx_am_addr_t src // Source (2 bytes) nx_uint8_t length // Payload Length (1 byte) nx_am_group_t group // Group ID (1 byte) nx_am_id_t type // Active Message Handler Type (1 byte), some enum value that you can def...
Read more