File tree Expand file tree Collapse file tree 3 files changed +0
-22
lines changed Expand file tree Collapse file tree 3 files changed +0
-22
lines changed Original file line number Diff line number Diff line change @@ -187,8 +187,6 @@ jobs:
187
187
micromamba activate xeus-lite-host
188
188
python -m pip install jupyterlite-xeus jupyterlite-core jupyterlab notebook libarchive-c
189
189
jupyter lite build --XeusAddon.prefix=${{ env.PREFIX }} --contents notebooks/xeus-cpp-lite-demo.ipynb --output-dir dist
190
- cp ${{ env.PREFIX }}/bin/xcpp.data dist/extensions/@jupyterlite/xeus/static
191
- cp ${{ env.PREFIX }}/lib/libclangCppInterOp.so dist/extensions/@jupyterlite/xeus/static
192
190
193
191
- name : Upload artifact
194
192
uses : actions/upload-pages-artifact@v3
Original file line number Diff line number Diff line change @@ -153,15 +153,6 @@ python -m pip install jupyterlite-xeus jupyter_server
153
153
jupyter lite build --XeusAddon.prefix=$PREFIX --contents xeus-cpp/notebooks/xeus-cpp-lite-demo.ipynb
154
154
```
155
155
156
- We now need to shift necessary files like ` xcpp.data ` which contains the binary representation of the file(s)
157
- we want to include in our application. As of now this would contain all important files like Standard Headers,
158
- Libraries etc coming out of emscripten's sysroot. Assuming we are still inside build we should do the following
159
-
160
- ``` bash
161
- cp $PREFIX /bin/xcpp.data _output/extensions/@jupyterlite/xeus/static
162
- cp $PREFIX /lib/libclangCppInterOp.so _output/extensions/@jupyterlite/xeus/static
163
- ```
164
-
165
156
Once the Jupyter Lite site has built you can test the website locally by executing
166
157
167
158
``` bash
Original file line number Diff line number Diff line change @@ -174,17 +174,6 @@ for testing execute the following
174
174
python -m pip install jupyterlite-xeus jupyter_server
175
175
jupyter lite build --XeusAddon.prefix=$PREFIX --contents xeus-cpp/notebooks/xeus-cpp-lite-demo.ipynb
176
176
177
- We now need to shift necessary files like `xcpp.data ` which contains the
178
- binary representation of the file(s) we want to include in our
179
- application. As of now this would contain all important files like
180
- Standard Headers, Libraries etc coming out of emscripten's sysroot.
181
- Assuming we are still inside build we should do the following
182
-
183
- .. code :: bash
184
-
185
- cp $PREFIX /bin/xcpp.data _output/extensions/@jupyterlite/xeus/static
186
- cp $PREFIX /lib/libclangCppInterOp.so _output/extensions/@jupyterlite/xeus/static
187
-
188
177
Once the Jupyter Lite site has built you can test the website locally by
189
178
executing
190
179
You can’t perform that action at this time.
0 commit comments