2016-02-24T02:01:56Z ekinmur joined #ccl
2016-02-24T02:24:13Z emaczen joined #ccl
2016-02-24T02:27:11Z emaczen: Did anyone answer my questions from two hours ago? My compute appears to have logged me off and I was away and I don't see anything in the irc-logs.
2016-02-24T02:28:35Z rme: emaczen: I am afraid I don't see any answers.  You are probably going to have to go looking Objective-C Cocoa-land.
2016-02-24T02:29:15Z rme: And you're right about the logs.  I wonder why ccl-logbot is not working.  I will have to look at it tomorrow.
2016-02-24T02:33:36Z emaczen: Where can I find that CCL picture app?
2016-02-24T02:33:50Z rme: I'll put it on GitHub this week.
2016-02-24T02:34:12Z emaczen: rme: cool -- that should probably be helpful.
2016-02-24T02:34:49Z rme: Well, it won't help you do tricky stuff with NSScrollView.
2016-02-24T02:35:16Z emaczen: It should be generally nice for the future at least.
2016-02-24T02:35:36Z emaczen: pjbh: Is this pjb? What is the h?
2016-02-24T02:38:51Z emaczen: rme: I think you are right... I'm going to have to start finding these type of objective-c projects and building it with xcode or something.
2016-02-24T04:12:26Z ekinmur quit (Quit: My Mac has gone to sleep. ZZZzzz…)
2016-02-24T06:27:10Z jackdaniel: hey o/ is there a simple way to install ccl from svn trunk in the another directory? (not only image, but also docs etc)
2016-02-24T07:16:57Z emaczen left #ccl
2016-02-24T08:14:33Z rme quit (Quit: rme)
2016-02-24T08:14:34Z rme quit (Quit: rme)
2016-02-24T14:25:37Z rme joined #ccl
2016-02-24T17:21:45Z billstclair: jackdaniel: You can install it anywhere you want. The problem you’re probably encountering is that the “ccl” and “ccl64” scripts default CCL_DEFAULT_DIRECTORY to /usr/local/src/ccl
2016-02-24T17:22:07Z billstclair: You can fix that with either a global value of CCL_DEFAULT_DIRECTORY, or, the way I do it:
2016-02-24T17:23:01Z billstclair: Make a soft link from “ccl” somewhere in your PATH to the executable you want to run, e.g. dx86cl64 for Mac or lx86cl64 for linux. E.g.:
2016-02-24T17:23:19Z billstclair: ln -s …/path/to/ccl/dx86cl64 ~/bin/ccl
2016-02-24T17:24:07Z billstclair: Then, assuming ~/bin is in PATH, “ccl” will start it from the command line
2016-02-24T17:25:47Z jackdaniel: but I can also do something like a custom "ccl" script like: 'CCL_DEFAULT_DIRECTORY=/my/custom/ccl/path /my/custom/ccl/path/lx86cl64 "\@$"'?
2016-02-24T17:30:05Z rme: If set, CCL_DEFAULT_DIRECTORY is used to determine the location of the ccl: logical host.  If it is not set, the ccl: logical host will refer to the directory containing the heap image name.
2016-02-24T17:30:39Z jackdaniel: ah, so I don't need to set it, thanks
2016-02-24T17:31:15Z rme: So, if you do "/usr/local/src/ccl/dx86cl64 -I /tmp/foo.image", for example, (probe-file "ccl:") => #P"/private/tmp/" (on my OS X system).
2016-02-24T17:32:29Z jackdaniel: right. My question was about some script to copy all files but the build ones, but this information is useful too. I'm writing a small issue for the next ECL Quarterly about how to build various FOSS lisps from source
2016-02-24T17:33:04Z jackdaniel: sbcl for instance has ./install.sh, while ecl installs to the directory given with --prefix. With CCL I was confused at first which files to copy
2016-02-24T17:33:37Z jackdaniel: but I peaked in the PKGBUILD from ArchLinux and copied the same files
2016-02-24T17:40:52Z rme: There's not really an official way to install CCL.  The general assumption is that ccl (binaries + interface database + sources) will be in the ccl directory (the ccl: logical host).  "Installation" is putting a tiny "ccl" shell script somewhere that does 'exec /path/to/ccl/lx86cl64 "$@"' or whatever.
2016-02-24T17:41:11Z rme: I don't know what the packages for Arch or other Linux distribution do.
2016-02-24T17:55:00Z jackdaniel:  basically what you said, but also remove fasls and x86 imaga (on 64bit system)
2016-02-24T18:53:23Z jackdaniel quit (Ping timeout: 248 seconds)
2016-02-24T19:00:57Z jackdaniel joined #ccl
2016-02-24T21:30:42Z hydan joined #ccl