JeremyYao commented on PR #1277:
URL: https://github.com/apache/daffodil-vscode/pull/1277#issuecomment-3362687087

   > As a quick workaround, try removing the _@omega-edit/client_ package in 
the dfdl extension _node_modules_. Then in the Omega Edit repo, after a 
successful build and install via `cmake`, run:
   > 
   > ```shell
   > packages/build.sh -fl <path/to/dfdl/extension>`
   > ```
   > 
   > The key difference here being the inclusion of the `-f` (_force_) option 
which cleans the `yarn` cache directory then proceeds to create the OE package 
links.
   
   I'm still running into the same issue after following the steps. 
   
   <img width="436" height="178" alt="image" 
src="https://github.com/user-attachments/assets/763ff15a-0239-4b29-a96e-c1d89094b478";
 />
   
   For tracing my steps, I ran 
   
   ```bash
   git clean -fdx
   cmake -S . -B _build -DCMAKE_BUILD_TYPE=Debug -DBUILD_DOCS=NO 
-DBUILD_EXAMPLES=NO -DBUILD_SHARED_LIBS=YES
   cmake --build _build --config Debug
   ctest --build-config Debug --test-dir _build/core --output-on-failure
   cmake --install _build --config Debug --prefix _install
   yarn install
   yarn workspace @omega-edit/server package
   yarn workspace @omega-edit/client package
   yarn workspace @omega-edit/client test
   ```
   
   inside of my Omega Edit repo in WSL
   
   I then ran 
   
   ```
   git clean -fdx; yarn; yarn package
   ``` 
   
   in the extension repo and then proceeded to remove the 
node_modules/@omega-edit/client in the extension repo. 
   
   Inside of WSL, I linked via `./build.sh -fl 
/mnt/c/Users/jeremy.yao/repos/space\ test/daffodil-vscode-ctc/` after modifying 
the `destination_dir=$1` line to `destination_dir=$OPTARG`
   
   and then encountered the above screenshot. 
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to