Forum > General
Lazarus "main" fails to build on macOS Intel and ARM64
trev:
--- Code: Bash [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---/Applications/Xcode.app/Contents/Developer/usr/bin/make -C components/chmhelp/lhelp distclean/bin/rm -f lhelp lhelp.o lhelp.bclibplhelp.a libimplhelp.a/bin/rm -f lib/aarch64-darwin/basecontentprovider.o lib/aarch64-darwin/chmcontentprovider.o lib/aarch64-darwin/chmdataprovider.o lib/aarch64-darwin/chmspecialparser.o lib/aarch64-darwin/filecontentprovider.o lib/aarch64-darwin/lhelp.o lib/aarch64-darwin/lhelpcore.o lib/aarch64-darwin/lhelpstrconsts.o lib/aarch64-darwin/basecontentprovider.ppu lib/aarch64-darwin/chmcontentprovider.ppu lib/aarch64-darwin/chmdataprovider.ppu lib/aarch64-darwin/chmspecialparser.ppu lib/aarch64-darwin/filecontentprovider.ppu lib/aarch64-darwin/lhelpcore.ppu lib/aarch64-darwin/lhelpstrconsts.ppu lib/aarch64-darwin/lhelpcore.lfm lib/aarch64-darwin/lhelp.or lib/aarch64-darwin/lhelp.res /bin/rm -rf units/bin/rm -rf bin/bin/rm -f *.o *.bc *.ppu *.rst *.s *.a *.so *.ppl/bin/rm -rf *.sl/bin/rm -f fpcmade.* Package.fpc *.fpm/bin/rm -f script*.res link*.res *_script.res *_link.res/bin/rm -f ./ppas.sh *_ppas.sh ppas.sh ppaslink.sh/Applications/Xcode.app/Contents/Developer/usr/bin/make -C examples cleanmake[1]: *** No rule to make target `clean'. Stop.make: *** [purge] Error 2
Same error on Intel and ARM64 macOS.
Related to recent examples commits.
JuhaManninen:
make -C examples clean
OK, the projects were structured into subdirectories.
I am away from my development computer now, I will study the issue soon...
[Edit]@Trev, what is the command that you actually run?
I can do "make clean all" for Lazarus sources without errors.
Typing "make -C examples clean" gives the error but I don't need to type it.
trev:
The commands my daemons run to make my daily Sourceforge macOS aarch64 and Intel Lazarus snapshots is respectively:
--- Code: Bash [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---make clean distclean all LCL_PLATFORM=cocoa CPU_TARGET=aarch64 bigidemake clean distclean all LCL_PLATFORM=cocoa CPU_TARGET=x86_64 bigide
This has worked for the last 4 11 months.
trev:
--- Quote --- clean deletes files that 'bigide' creates. It does not clean up all possible
targets. Clean other target: make clean LCL_PLATFORM=qt
distclean Clean all targets and common leftovers.
--- End quote ---
The culprit is distclean. I assume there's a makefile change needed.
dbannon:
Trev, as the origin of those example changes, maybe it is down to me ?
I am sure your script is not expecting a Makefile in each and every directory ? That has not been the case in the past, there is no point in making all those examples in bulk.
But there was a Makefile in ~/examples itself. Seemed to me totally redundant and it was not being called, in my tests, by, eg, a "make clean bigide".
It appears to be intended to build "simple" examples and, as you found, clean up afterwards. Would require some cleaning up ! The definition of "simple" examples seems to be the ones loose in the ~/examples dir, not the ones in their own dir. I have either removed or moved all such examples.
Many were demonstrating how to use the various components before we had the ObjectInspector and are generally irrelevant now. As they were first seen, they were causing a lot of confusion with new users. I have retained a few to demonstrate the technique in case some has a special requirement but its sure not how we encourage people to work generally.
If its really necessary, maybe a dummy Makefile that does nothing, is the answer ?
Note that ~/components/examplewindow does not have a Makefile either, its a standalone Package and, IMHO, should not have a Makefile. But ...
Davo
EDIT : Post post thought, previously, building all those quite unnecessary examples and shipping them with the Install Package ? Undesirable.
Navigation
[0] Message Index
[#] Next page