freenode/#clasp - IRC Chatlog
Search
1:23:49
drmeister
cytoscape-jupyter was put online about a year ago - since then there have been three (3!) major revisions of 'webpack'. Cytoscape-jupyter needs webpack version 1.12.14. Once I evaluated the commands I just pasted in the bash shell I was able to run 'make' in cytoscape-jupyter and it got a lot further.
1:38:07
drmeister
After installing webpack@1.12.14 (and maybe uninstalling the other webpack first) I ran 'make' again in jupyter-cytoscape and then the demo started up.
1:39:52
drmeister
The 'make' starts up jupyterlab on my machine and the widget doesn't work. But when I backup to the jupyter file browser...
1:41:09
drmeister
and start the smallNetwork.ipynb and then shift-click through the entire notebook - then the demo works.
1:45:12
Kevslinger
This is splendid. Once we figure out how the Python packages the JSON, all we need to do is mimic it
1:51:01
stassats
clasp itself has multiple compilers, interpreters, garbage collectors, and requires another lisp implementation to build
11:23:07
frgo
Hello all - I know it's early for US but, by any chance, are you drmeister or Bike online? I cloned externals-clasp and clasp branch dev and get a build error - is this a known issue?
12:01:27
attila_lendvai
I'm wondering now that I've integrated pump into the build, maybe its output should be deleted from the repo and moved under build/...
12:01:58
attila_lendvai
I'd fancy some opinion on that. python is needed for the build anyways, so there's no reason to keep the pump.py output checked into the repo
12:03:58
frgo
The output are header files. They are needed for C++ level compile. Do you plan to regenerate those every time a compile is done?
12:05:32
frgo
Ok - distclean cleans the build directory, in fact deletes it. So yes, it *should* work.
12:06:51
attila_lendvai
I'll create the PR now anyways to gather feedback, and I'll do that afterwards. then I need to run a full build to test it...
12:10:08
attila_lendvai
frgo: it's black magic... one thing that I needed was bld.add_group(). it's kinda like a separator between two groups of parallel tasks. then there's the ext_out property on tasks, that I don't understand much, but they do affect the order (i.e. tasks with '.h' ext_out must be finished before tasks with '.o' ext_out can start). and then there's new_task(..., after = [ some_other_task_instance ])
12:11:26
attila_lendvai
no, it's waf. it's full of complex DWIM behavior that hurts making progress way more than helps it
12:11:53
frgo
Ok - I figure it's an extension thing. This happens only for the extension I am implementing.