On Tue, Apr 9, 2019 at 2:44 PM Stephen Foster <step...@thoughtstem.com> wrote:
> > I've always assumed that any correct Racket code can be run during setup's > documentation-building time. If this isn't true, how can I know which > Racket code can be used in this way and which can't? > > I just wanted to +1 this thread; as I've been working on documentation where I'd like to either 1) procedurally generate images as part of the docs, or 2) have parts of the library that generate graphical output, I run into import issues at setup time that cause the build to fail. These are probably all variants of the OSX/non-main place problem. I've been considering moving to a two-phase documentation build process, where I have a Makefile to run Racket code to generate static images, and then drive Scribble to generate the documentation. This way, the documentation build process will succeed. In the end, that might be more portable/easier for distribution anyway... Cheers, M -- 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.
