Re: [fpc-pascal] Re: Compilation Error At revision 25270.
On 8/18/2013 02:52, Reinier Olislagers wrote: On 17/08/2013 19:34, waldo kitty wrote: [...] so you started as #1 above and svn up to #2... when you run make clean, the old mylib.o,.a,.ppu files are still in \projects\myproject somewhere and may be used by the compiler instead of those that should be in \projects\libs where you moved your mylib.pas file to... is that clearer now?? I'll take you at your word. I don't use makefiles in my projects. right but others (FPC and Lazarus) do... not to mention that it was an example and i didn't feel like laying out the whole lazarus tree to show it from that perspective... in any case, failing to run "make clean" or "make disclean" /before/ "svn up" can lead to problems with old libraries being left in old locations when files are moved... we've seen this exact situation with Lazarus in numerous cases... the standard response has been to run the "Clean up build files" option which removes all .o, o., and .ppu files so they can be rebuilt from the proper source files from their (new) locations... question: at what point does your updater tool perform "make clean" or "make distclean"? before or after or both, before and after, the svn update? -- NOTE: No off-list assistance is given without prior approval. Please keep mailing list traffic on the list unless private contact is specifically requested and granted. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: Compilation Error At revision 25270.
On Sun, 18 Aug 2013 09:43:37 -0400 waldo kitty wrote: > On 8/18/2013 02:52, Reinier Olislagers wrote: > > On 17/08/2013 19:34, waldo kitty wrote: > [...] > in any case, failing to run "make clean" or "make disclean" /before/ "svn up" > can lead to problems with old libraries being left in old locations when > files > are moved... we've seen this exact situation with Lazarus in numerous > cases... > the standard response has been to run the "Clean up build files" option which > removes all .o, o., and .ppu files so they can be rebuilt from the proper > source > files from their (new) locations... "make clean" only cleans up the Lazarus files. "Clean up build files" cleans up the user project and packages too. Mattias ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: Compilation Error At revision 25270.
On 18/08/2013 15:43, waldo kitty wrote: > On 8/18/2013 02:52, Reinier Olislagers wrote: >> On 17/08/2013 19:34, waldo kitty wrote: > question: at what point does your updater tool perform "make clean" or > "make distclean"? before or after or both, before and after, the svn > update? fpcup? It runs make distclean before svn update. [1] There used to be (don't know if I left it in) "nuclear clean" mode that does a recursive delete of *.ppu, *.a, *.o before the svn up. [1] it also stashes diffs of any version-controlled files before doing svn up. The user can choose to try and restore/apply that diff afterwards. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: Compilation Error At revision 25270.
On 8/18/2013 09:49, Mattias Gaertner wrote: On Sun, 18 Aug 2013 09:43:37 -0400 waldo kitty wrote: On 8/18/2013 02:52, Reinier Olislagers wrote: On 17/08/2013 19:34, waldo kitty wrote: [...] in any case, failing to run "make clean" or "make disclean" /before/ "svn up" can lead to problems with old libraries being left in old locations when files are moved... we've seen this exact situation with Lazarus in numerous cases... the standard response has been to run the "Clean up build files" option which removes all .o, o., and .ppu files so they can be rebuilt from the proper source files from their (new) locations... "make clean" only cleans up the Lazarus files. "Clean up build files" cleans up the user project and packages too. ahh! thanks for the clarification... "Clean up build files" does for projects what "clean" and "distclean" do for FPC and Lazarus... that does make sense since the projects cannot be known by FPC's and Lazarus' building makefiles :) -- NOTE: No off-list assistance is given without prior approval. Please keep mailing list traffic on the list unless private contact is specifically requested and granted. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Embedded ARM7 and long strings
Am 24.07.2013 09:07, schrieb Carsten Bager: > The {$LONGSTRINGS OFF} directive is given at the beginning of the program, > and that > eliminates any problems with "long strings" using the 2.05 compiler. That > does not seem to > work with the new compiler. > > Is there a way around this problem? I applied a fix in r25283 which should help you. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal