Jump to content

Pavel

Administrators
  • Content Count

    1,471
  • Joined

  • Last visited

Everything posted by Pavel

  1. I suspect this is because of protection system we use though I never saw such troyan warning in my development environment. Please try an experimental build with minimal/no protection from http://www.sourceboost.com/CommonDownload/Binaries/sourceboostv801.exe Update: I checked multiple files included into the installation on Virus Total and it seems that executables built under Visual Studio 2008 generate such false positives. I created a test program that consists of an empty _tmain function, built it with Visual Studio 2008 and tested under Virus Total. It reported a 1 false positive. Another update: I think I have sorted out the virus total false positives. The new 8.01 build doesn't trigger any reports. Will publish it later today. Pavel
  2. SourceBoost 8.00 is now FREE and available from www.sourceboost.com
  3. After a long break we are about to release a new version which will be free with optional donation to support developers. Regards, Pavel
  4. After a long break we are about to release a new compiler build. The BoostC compiler family will be free with optional donation to support developers. Regards, Pavel
  5. That's an useful report. The error happens because the SourceBoost code fails to parse some text that contains non-english characters (maybe somewhere in a directory name). Does this happen on your computer? Regards, Pavel
  6. We do add support for the new PICs from time to time but now very often. The 18F26K42 and alike are a bit different from the existing PICS as they offset SFRs by 0x3000 and our linker does not support this yet. We looking into this but can't guarantee this will be supported (at least soon ). Regards, Pavel
  7. Yes Chameleon does work with Novo. The code you mentioned is generated by linker so there is no difference if BoostC or Chameleon is used. One can even mix OBJ files generated by BoostC and Chameleon in the same project. Regards, Pavel
  8. Compiler hanging is not good and we will look into this but your code does not look correct either. Everything inside the asm{} block should be assembly language. Anything else including C statements like _tblptru = 0 will not work. Regards, Pavel
  9. I can confirm this issue for the BoostC compiler family. The Chameleon compiler however handles this code well. Regards, Pavel
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. Cam you email your source file to support@sourceboost.com Regards, Pavel
  16. 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
  17. You need to show us your GsmRemote.c file or at least its first 18+ lines. Regards, Pavel
  18. 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).
  19. 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)
  20. 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
  21. You can use your v7 license key with SourceBoost v6. Regards, Pavel
  22. 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
  23. 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
  24. 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
×
×
  • Create New...