Clojurians
#lumo
<
2017-02-19
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

isaac11:02:31

I made a simple tool for lumo users. it’s inspired by boot-clj https://github.com/gfZeng/cljs-boot

hlolli12:02:25

nice, Im as I write struggling to organize a lumo based project, as some dependencies are from npm and others clojars (andre for example). Calvin seems to try to take leiningen approach of organizing a self-hosted cljs project. I wonder if more people are writing build-tools at the moment. But I like this approach even more, keeping everything in package.json, clean.

dominicm19:02:29

@anmonteiro did you get a chance to check out the depdnecy stuff?

anmonteiro21:02:32

@dominicm thanks for the reminder, going through it now!

anmonteiro21:02:22

@dominicm my preliminary analysis tells me this is a quirk of the packaging process (Nexe’s problem)

anmonteiro21:02:37

I think it can be fixed upstream so I’m working on that

anmonteiro21:02:43

nice catch, btw

dominicm21:02:19

@anmonteiro that's awesome. It was an intense afternoon figuring it out :stuck_out_tongue:

pesterhazy22:02:12

when I build lumo I get

----> cp /Users/pe/prg/lumo/tmp/node/7.5.0/node-v7.5.0/out/Release/node build/lumo
----> copied
Finished bundling. Nexe binary can be found in build/lumo
### Compiling Macro Namespaces
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/pe/prg/lumo/build/lumo
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/pe/prg/lumo/build/lumo
  Expected in: /usr/lib/libSystem.B.dylib

./scripts/aot-bundle-macros.sh: line 18: 50754 Trace/BPT trap: 5       $(pwd)/build/lumo --quiet -c target -sdk lumo-cljs/out/macros-tmp  <<REPL_INPUT
(require-macros 'lumo.repl 'clojure.template 'cljs.spec 'cljs.spec.impl.gen 'cljs.test 'cljs.reader)
REPL_INPUT

pesterhazy22:02:27

that's current master on macos

anmonteiro22:02:29

is that on Linux?

anmonteiro22:02:55

that’s really weird

anmonteiro22:02:01

neither me nor the CI gets it

pesterhazy22:02:39

I'm still on macos 10.11 not the latest 10.12, could that have something to do with it?

anmonteiro22:02:25

@pesterhazy that looks like an issue building Node.js

pesterhazy22:02:32

looks like a common macos xcode issue

pesterhazy22:02:23

I'l try reinstalling the xcode command line tools

anmonteiro22:02:42

@pesterhazy maybe try to build against 7.4.0 locally. change this line https://github.com/anmonteiro/lumo/blob/master/scripts/package.js#L72

pesterhazy22:02:13

if rm'ing tmp enough to ensure a clean node build?

pesterhazy22:02:38

I'll give that a try

pesterhazy22:02:23

by the way, can I use boot dev to make changes continuously to lumo?

anmonteiro23:02:57

@pesterhazy yes

anmonteiro23:02:17

just run boot dev in a terminal window

anmonteiro23:02:27

in another terminal test your changes with yarn dev

anmonteiro23:02:33

I just opened the Lumo wiki

anmonteiro23:02:49

Feel free to add a page describing the process if you want