Jump to content

JorgeF

EstablishedMember
  • Content Count

    314
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JorgeF

  • Rank
    Super Enthusiast

Profile Information

  • Gender
    Male
  • Location
    PT @ Europe, third rock from the Sun
  1. Hi It shouldn't be a problem, AFAIK it can be done with any toolchain and/or IDE out there. For header (.h) files you just need to put the path in the #include statement. For source files (.c) you have to provide those extra paths to the makefile. Besides this universal steps, In MPLABX, specifically, you can include extra folders in your project tree. Best regards Jorge
  2. Hi AFAIK CoostC/C++ never supported 16bit or 32bit devices, only 8bit ones. Best regards Jorge
  3. Hi For sure I would like to have a linux version of BoostC. I have a licenced V7 and its one of the few things that makes me keep a Windows partition on my laptop. If possible, fully integrated in MplabX Best regards Jorge
  4. Hi Did you try to contact support? support@sourceboost.com Best regards Jorge
  5. Hi Yep. Its not the first time that an anti-virus triggers a false positive. Surprisingly it rarely happens as all it takes is a shared sequence of code with a known virus. With the millions of programs out there in the world, it could happen a lot more. Good you have your problem sorted out. Best reagrds Jorge
  6. Hi That's strange. Might it be that you are working with a very old project, created under a previous version? How does it behave with a brand new project? In my installation (7.43), all the compilers have the underscore in the name, also the linker. BTW, don't forget to do a good virus/malware scan on your PC. Best regards Jorge
  7. Hi I might be wrong, but. I have a faint memory of such a change somewhere along the V7.xx versions. At the time the subject was discussed/explained in the forum, maybe you should take a look at it. What is the exact version you are using?
  8. Hi That is strange, I installed the Sourceboost IDE with Boost C and goodies licences in a new laptop (3 weeks ago) running Win 10 64bit up to date without any issues. Best regards Jorge
  9. Hi Pavel Thank you for the quick reply. Good to know. Its been a long time since I looked at the NOVO source, so my memory tricked me on remembering "...this only works because of linker magic...". Anyhow I wasn't aware that the linker was the same for both compilers, kind of assumed it was 2 completelly separated toolchains. Best regards Jorge
  10. Hi I was wondering. Does the Chameleon compiler support the NOVO RTOS. AFAIK the BoostC compiler does generate a piece of special to code to execute the task switching on the NOVO scheduler. It would be nice if Chameleon had the same feature. Best regards Jorge
  11. Hi Good you found it. But its a fact that the BoostC compiler is quite weak in terms of error reporting. I've seen that error, "failure", for all kinds of errors. In fact its quite rare to see other error messages. Best regards Jorge
  12. Hi Usualy the forums are more targeted at experience exchange between users than to technical support. Same happens with the Microchip forum and a few others I know. Best regards Jorge
  13. Hi Confirmed, both for C++ and C. Did you try to send an email to support@sourceboost.com ? Best regards Jorge
  14. Hi I missed this topic in due time,so I don't know if this repply is usefull, but here it goes. That is a nice ASM trick, but I think its uneeded in 'C' and also undesired. Its not a good idea to directly manipulate the stack when using a compiled language, because you don't control how the compiler handles the stack. Also bear in mind that due to the limited stack size and specific stack access instructions of the 8 bit PICs, BoostC and other compilers implement a so called "software stack" to handle parameters and automatica variables. The hardware stack is
×
×
  • Create New...