Hi group, I use Racket in an embedded linux system. My normal development process is to write Racket code in Windows, transfer this to the embedded computer, and then use raco make in the Debian system. But when the system is powered on, it doesn't boot to Debian, it boots to a busybox OS where the filesystem is read-only, and the paths are not the same.
To this end, the busybox OS runs a startup script which calls racket directly to run the main file. This all works fine, but I have started to wonder about two things: 1) does raco make build in any absolute path dependencies? Should I instead remount the filesystem as read/write in busybox and run "raco make" there, since the busybox filesystem has different paths than the Debian filesystem? 2) suppose I run raco make on a board and copy the result out to a USB stick with a FAT filesystem which can't preserve things like execute permissions, then copy this back to a new board. Should I expect that the racket executable will have some problems with the previously-used "compiled" folders? Thanks for any insight here. Deren -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
