This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-28
Channels
- # admin-announcements (2)
- # alda (5)
- # arachne (4)
- # beginners (49)
- # boot (92)
- # capetown (3)
- # cider (9)
- # cljs-dev (6)
- # cljs-edn (1)
- # cljsjs (29)
- # cljsrn (4)
- # clojure (65)
- # clojure-android (1)
- # clojure-berlin (2)
- # clojure-chicago (2)
- # clojure-gamedev (2)
- # clojure-greece (11)
- # clojure-india (1)
- # clojure-japan (1)
- # clojure-new-zealand (2)
- # clojure-quebec (2)
- # clojure-russia (49)
- # clojure-spec (73)
- # clojure-uk (38)
- # clojurescript (118)
- # clojutre (4)
- # community-development (17)
- # cursive (3)
- # data-science (1)
- # datascript (1)
- # datomic (17)
- # emacs (6)
- # euroclojure (2)
- # events (2)
- # immutant (30)
- # keechma (11)
- # leiningen (4)
- # luminus (2)
- # off-topic (19)
- # om (14)
- # onyx (28)
- # planck (9)
- # re-frame (11)
- # reagent (35)
- # ring-swagger (4)
- # schema (4)
- # slack-help (6)
- # spacemacs (2)
- # specter (11)
- # testing (4)
- # untangled (88)
- # utah-clojurians (2)
- # vim (2)
- # yada (9)
@mfikes: hmm, can't seem to find any way to build WebKit for only C. There's --minimal
and --webkit-only
flags...
@mfikes: so, I obtained a debug JavaScriptCore.framework
via the command: /Tools/Scripts/build-webkit --debug --cmakeargs="-DSHARED_CORE=ON"
. However, trying to specify it for our program is proving difficult.
I've tried:
1) add the parent of JavaScriptCore.framework
via -F
(i.e., .../webkit/WebKitBuild/Debug
) and then -framework JavaScriptCore
. But this just picked up the release version installed in /Library/Frameworks.
2) Variation of above but using -L
and -l
instead of -F
and -framework
(stupid I know but someone on the internet suggested it so I tried it :))
3) Variation of #1 but with JavaScriptCore.framework
renamed to JavaScriptCoreDebug.framework
and -framework JavaScriptCoreDebug
. <-- this seems most promising as /Library/Frameworks
is locked down-- no modifications or additions even as sudo. However, this failed-- it just couldn't find it at all.
I'm thinking that a 'deep rename' must be performed for this to work (and not merely a superficial 'folder rename').
[I think the .framework approach is vastly superior to my previous libtool-combined object file approach (as there were duplicate symbols forcing me to (hopefully intelligently but still likely not infallibly) choose the best candidates from a number of conflicting .o files].
[Oh, and I couldn't just specify all of the separate .o files in the linker flags as that caused the maximum shell command length to be exceeded].