Jump to content

Pavel

Administrators
  • Content count

    1,461
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Pavel

  • Rank
    Super Maniac

Contact Methods

  • Website URL
    http://www.sourceboost.com
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    Melbourne, Australia

Recent Profile Visitors

3,469 profile views
  1. Yes you can share the compiled libc binary but not the library sources. Please make sure the github users know the origin of the binary. Regards, Pavel
  2. We would like to reproduce this and we don't need your source code. Please email your project obj files and linker command line to support@sourceboost.com Regards, Pavel
  3. I tried your suggestions but could not reproduce this error Most likely it's just one particular line of code. Maybe you can remove portions of this code that contain IP of your customer and send us the resulting file and maybe even obfuscate it. We are releasing a new version very soon and it'll be nice if this fix makes its way in. Regards, Pavel
  4. Here are some notes how rom objects work in BoostC: - a rom object is always identified by one byte (that's why in the code above gbl_sw_id is 1 byte long) - when linker processes all its input files it makes a list of all rom objects and allocates IDs to them - linker generates code for all these rom objects that it puts into the code memory - linker generates a function that can extract any byte of any rom object using its ID and position/index - when compiler needs to generate code to access character in a rom object it uses an placeholder ID and character position/index and calls function that linker generates in the prev bullet. Later linker replaces this placeholder ID with an actual object ID. Chameleon does not yet support rom objects. Support for rom objects will be added to Chameleon in the upcoming 7.43 release. Regards, Pavel
  5. When compiling a file the first thing the compiler does it splitting preprocessed source file into lines. If it fails it spits out the error that you quoted. Normally this process is very straightforward and there shouldn't be any errors (hence the error is so brief) but looks like we missed something in this parser (Chameleon is still in beta stage). Can you email your source file along with the compiler command line to support@sourceboost.com so we can investigate. Regards, Pavel
  6. Cam you email your source file to support@sourceboost.com Regards, Pavel
  7. This is a bug. Please try a fix available from http://www.sourceboost.com/CommonDownload/Fixes/c_pic16.zip (download and unzip it into your SourceBoost installation directory, it will replace the original chameleon pic16 compiler). Thanks for reporting this. Regards, Pavel
  8. You need to show us your GsmRemote.c file or at least its first 18+ lines. Regards, Pavel
  9. Try changing random_int = rand(); to random_int = rand() >> 1; This will reduce the possible random range by half but your code will operate on the positive half of the int range (when itoa implicitly converts unsigned to signed it will deal with lover half of the unsigned range which converted to signed will contain only positives).
  10. You access function argument correctly. Must be something else that causes the problem. Have you included system.h? If W is undefined you'll get same error (to check replace W with 0)
  11. A TDF file is required for build but only the core data from it is used. You need to have a TDF file that has at least minimal data like in _PIC18minimal.TDF There is no document that lists all options that can be used in TDF. You need to check the existing TDF files for examples. Regards, Pavel
  12. You can use your v7 license key with SourceBoost v6. Regards, Pavel
  13. Error with PIC18F25K40

    Well spotted. This error affects several other recently added targets as well. The fix you provided is correct too. Affected files: PIC18F24K40.TDF PIC18F25K40.TDF PIC18F26K40.TDF PIC18F27K40.TDF PIC18F45K40.TDF PIC18F46K40.TDF PIC18F47K40.TDF PIC18F65K40.TDF PIC18F66K40.TDF PIC18F67K40.TDF PIC18LF24K40.TDF PIC18LF25K40.TDF PIC18LF26K40.TDF PIC18LF27K40.TDF PIC18LF45K40.TDF PIC18LF46K40.TDF PIC18LF47K40.TDF PIC18LF65K40.TDF PIC18LF66K40.TDF PIC18LF67K40.TDF
  14. Chameleon has much better template support including meta programming. It does not however support member functions including constructors and destructors or inheritance (inheritance is not too difficult to add but probably does not make much sense if member functions are not supported). Regards, Pavel
  15. Chameleon has a number of advantages over BoostC. Some technical differences: - faster compilation - native floating point support - native bitfield support Current release of Chameleon does not have any license limitations and is free. Another important difference is in the way how compiler generates code. In BoostC user can't control this while in Chameleon almost all aspects of code generation can be customised by editing system headers located in include\sys directory. Regards, Pavel
×