mingw32-make PLATFORM=PLATFORM_DESKTOP spams me with errors (raylib) - raylib

Using the cmd "mingw32-make PLATFORM=PLATFORM_DESKTOP" (without the >"<) on the src folder in the raylib-master folder spams me with these kind of errors "C:\Users\User\AppData\Local\Temp\cckc59DX.s:109: Error: invalid instruction suffix for push'"
"C:\Users\User\AppData\Local\Temp\cckc59DX.s:129: Error: unsupported syntax for `call'" There are NOT 1, NOT 2, NOR 3, IT'S 46080 ERROS STRAIGHT
How to reproduce error:
Step 1: Install raylib from the official site.
Step 2: Follow the tutorial on how to install Raylib in the official wiki or a youtube video.
Step 3: Use VS Code and run example code for VSCODE.
Step 4: It worked for the first time but not in the second one.
Step 5: Run mingw32-make PLATFORM=PLATFORM_DESKTOP on src in raylib-master or the not master raylib library.
Step 6: Get spammed with errors.
Step 7: Cry because nothing has worked for you.

Related

How I can Add Jest as a dev Dependency as first task

Task 1: Add Jest as a devDependency
Open terminal. Make sure that it's pointing to jest-testing directory.
Install the jest npm package using the npm install command and the --save-dev flag.
Verify that the installation was completed successfully by opening the package.json file and confirming that the "devDependencies" entry lists jest similar to the following:
"devDependencies": {
"jest": "^28.0.0"
}
Task 2: Update the test entry
In the package.json file, locate the "scripts" entry, and inside of it, update the test entry to jest.
Task 3: Code the timesTwo function
Open the timesTwo.js file and add a function named timesTwo. The function should take number as input and return the value 2 multiplied by the number.
Export the timesTwo function as a module.
Task 4: Write the first test
Code a test call with the following arguments:
The description that reads: "returns the number times 2".
The second argument should expect the call to the timesTwo function, when passed the number 10, to be 20.
Task 5: Run the first test
With the terminal pointed at the jest-testing directory, run the test script using npm.
Task 1: Add Jest as a devDependency
use comands
cd jest-testing
node --version
npm --version
npm init -y
npm install --save-dev jest
Task 2: Update the test entry
enter image description here
Task 3: Code the timesTwo function
enter image description here
Task 4: Write the first test
enter image description here
Task 5: Run the first test
enter image description here

React Native Awesome Project Build Fail

Been trying to run the start up AwesomeProject file in VS Code but every time I run npx react-native run-ios...the build fail below comes up. Have looked through the stacks, comments, and questions here but I cannot find anything that is applicable.
Tried to change my terminal and Xcode to load with Rosetta but I get an error there too...
softwareupdate --install-rosetta
Installing Rosetta 2 on this system is not supported.
Not sure where to go from here...
** BUILD FAILED **
The following build commands failed:
PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/********/Library/Developer/Xcode/DerivedData/AwesomeProject-ekivgffrflagyugqmoefmykxoyqy/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/FBReactNativeSpec.build/Script-337605CB7CDF90939BEBF863ED22C375.sh (in target 'FBReactNativeSpec' from project 'Pods')
(1 failure)
info Run CLI with --verbose flag for more details.
I had this error too, i searched for hours...
What helped me was to downgrade version of react native to "react-native": "0.62.3" from 0.64
It also works with 0.63.
Others found this helpful: https://github.com/facebook/react-native/issues/32157

Expected linebreaks to be 'LF' but found 'CRLF' (Entando Framework)

I'm studying Entando framework , following step by step the Installing section.
I'm new to Node.
When I run the command npm start (paragraph 3.3.1), I get this error:
> app-builder#0.1.0 start C:\root_backup\workspace\entando app-builder\app-builder
> node scripts/start.js
Starting the development server...
Failed to compile.
./src/ui/common/form/RenderSelectInput.js
Line 1: Expected linebreaks to be 'LF' but found 'CRLF' linebreak-style
I found some solutions on the Internet (like this one), but it seems I can't apply to my scenario, since I can't find those files/scripts in my project.
Thank you for your precious help.
It seems that with the command npm run lint -- --fix is fixed

broadleaf - failed to execute goal

I am following these easy steps https://www.broadleafcommerce.com/docs/core/current/getting-started/running-locally
but I am stuck at step 2 already ´mvn spring-boot:run´ gives me the following error:
Failed to execute goal on project boot-community-demo-admin: Could not resolve dependencies for project com-mycompany-community:boot-community-demo-admin:jar1.0.0-SNAPSHOT.
feels like the pom.xml is not correct.
I believe it's looking for mycompany-community which doesn't exist http://nexus.broadleafcommerce.org/nexus/content/groups/community-snapshots/com/
thank you
You Can run using the eclipse it will run successfully with out giving any errors. here is the link to run using eclipse
Link: https://www.broadleafcommerce.com/docs/core/current/getting-started/ide-setup/eclipse-setup
It Will Work Fine While Running Using Eclipse. I Also checked in my System it is working fine with eclipseIDE.
It looks like you need to follow step 1c in the docs to mvn install from the root of the project. Did you do that part?

Node's Package Manager warning

I'm trying to install Hoodie
and after following the first steps in this tutorial http://www.sitepoint.com/tutorial-getting-started-hoodie/
in the step:
$brew install node
it shows me
Warning: node-0.10.33 already installed, it's just not linked
what does it mean?
To the first part of the question, this error means that you already have node installed on your system. You can likely find that install by using the command:
which node
Failing that,
locate node
I don't find any specific reference to the "it's just not linked" error statement, but the homebrew wiki refers to linking with the
brew link
command if/when the system fails to link (https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/FAQ.md#what-does-keg-only-mean)
The error itself would come out of homebrew/install.rb line 46 (https://github.com/Homebrew/homebrew/blob/face2a37b011856b270e7d95b305f31994b3a662/Library/Homebrew/cmd/install.rb)

Resources