4 ms·
Hmm... there's Python and CPP. src/socketify ├── __init__.py ├── __main__.py ├── asgi.py ├── cli.py ├── helpers.py ├── libsocketify_darwin_amd64.
by xwowsersx 4y ago
Hmm... there's Python and CPP.
src/socketify
├── __init__.py
├── __main__.py
├── asgi.py
├── cli.py
├── helpers.py
├── libsocketify_darwin_amd64.so
├── libsocketify_darwin_arm64.so
├── libsocketify_linux_amd64.so
├── libsocketify_windows_amd64.dll
├── loop.py
├── native
│ ├── Make.bat
│ ├── Makefile
│ ├── src
│ │ ├── libsocketify.cpp
│ │ └── libsocketify.h
│ └── uv_selector.txt
├── native.py
├── socketify.py
├── ssgi.py
├── status_codes.py
├── tasks.py
├── uv.py
├── uWebSockets
└── wsgi.py
I think the .so files are built from other source though? I'm not sure. In the makefile they are rm'd and then created. The linux workflow file, for example, has:
make linux
cd ../
git add libsocketify_linux_amd64.so
- cirospaciari 4y agoyou need to pull all git submodules too git submodule update --init --recursive --remote
- onedognight 4y agoAh, thanks! In my defense, the native/ directory contains the portable C++ source and the src/ directory contains a the native executables.
- cirospaciari 4y agoYes you are right!