Here are the first errors I got when I ran the make command on the cloned folder as is (PLEASE NOTE: These errors do not exist anymore, they are just to provide reference to make sure that I have not messed up anything in the core):
$ make
added 86 packages, and audited 87 packages in 11s
7 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
# generate javascript files
npm run build
> daa-displays@1.0.14 build
> tsc
src/daa-displays/daa-player.ts:56:54 - error TS2792: Cannot find module '../daa-server/utils/daa-types'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
56 import { ExecMsg, LLAData, ScenarioDescriptor } from '../daa-server/utils/daa-types';
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/daa-displays/daa-split-view.ts:51:25 - error TS2792: Cannot find module '../daa-server/utils/daa-types'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
51 import { LLAData } from '../daa-server/utils/daa-types';
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/daa-displays/daa-vertical-speed-tape.ts:55:35 - error TS2792: Cannot find module '../daa-server/utils/daa-types'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
55 import { ResolutionElement } from '../daa-server/utils/daa-types';
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/daa-server/daa-cppProcess.ts:45:26 - error TS2792: Cannot find module './utils/fsUtils'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
45 import * as fsUtils from './utils/fsUtils';
~~~~~~~~~~~~~~~~~
src/daa-server/daa-javaProcess.ts:46:26 - error TS2792: Cannot find module './utils/fsUtils'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
46 import * as fsUtils from './utils/fsUtils';
~~~~~~~~~~~~~~~~~
src/daa-server/daa-server.ts:41:8 - error TS2792: Cannot find module './utils/daa-types'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
41 } from './utils/daa-types';
~~~~~~~~~~~~~~~~~~~
src/daa-server/daa-server.ts:42:26 - error TS2792: Cannot find module './utils/fsUtils'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?
42 import * as fsUtils from './utils/fsUtils';
~~~~~~~~~~~~~~~~~
Found 7 errors in 6 files.
Errors Files
1 src/daa-displays/daa-player.ts:56
1 src/daa-displays/daa-split-view.ts:51
1 src/daa-displays/daa-vertical-speed-tape.ts:55
1 src/daa-server/daa-cppProcess.ts:45
1 src/daa-server/daa-javaProcess.ts:46
2 src/daa-server/daa-server.ts:41
Files: 151
Lines: 112453
Identifiers: 148159
Symbols: 125142
Types: 49121
Instantiations: 77238
Memory used: 213710K
I/O read: 3.10s
I/O write: 0.10s
Parse time: 5.69s
Bind time: 0.91s
Check time: 6.24s
Emit time: 1.52s
Total time: 14.36s
make: *** [Makefile:19: npm] Error 2
After this, I fixed the path errors which were redirecting the code to path that do not exist. Once this was done, I re-ran the make command, and there were 43 errors similar to the one below.
Error: DAABandsV2.java:47: error: package gov.nasa.larcfm.ACCoRD does not exist import gov.nasa.larcfm.ACCoRD.Alerter;
Code I am running:
cd utils; javac -cp ../../../daidalus-submodules/v2.0.2/Java/lib/DAIDALUS2.jar DAABandsV2.java DAAMonitorsV2.java && cp -f ../../../daidalus-submodules/v2.0.2/Java/lib/DAIDALUS2.jar ../DAIDALUSv2.0.2.jar && echo "Main-Class: DAABandsV2" > mf && jar umf mf ../DAIDALUSv2.0.2.jar DAABandsV2.class DAAMonitorsV2.class && rm -f mf
I tried to run the files individually in each folder, but I am not able to debug this error. I also tried to modify the path to look for the package, but it still didn't work.
It is my understanding that the package trying to be retrieved can be found at: daa-displays/daidalus-submodules/vx.0.2/Java/src/gov/nasa/larcfm.ACCoRD The file that is trying to retrieve this package and throwing the error is located at: daa-displays/dist/daa-logic/Makefile
I just found out in an issue of the project, that compilation is only supported on mac/linux machines (I suppose you opened it. Way to go 👍) but you are using Windows.
If you find a project with a README.md - file, you should always read that file about any information about how to compile and run the project. The file is usually rendered on the project main page on websites like GitHub:
In your case the following sections are extremely helpful:
The following software is necessary to compile and execute DAA-Displays
- NodeJS (v14.16.1 or greater) https://nodejs.org/en/download Java Open
- JDK (1.9 or greater) https://openjdk.java.net/install
- C++ compiler (gcc version 7.4.0 for Linux, Apple clang 11.0.0 for MacOS) Google
- Chrome (80.0.x or greater) https://www.google.com/chrome
- Download the latest release of DAA-Displays from the github repository.
- Open a terminal window and change directory to the daa-displays folder.
- Run make in the terminal window. This command will download the dependencies and create a folder dist/ with the distribution.
Let us know if you have more questions or if this solved your problem.