I'm using Buildroot 2015.08.01. I have this "weird" issue. We use an "external tree" setup here. I modified the .mk file to add/remove some libraries for the application to fix some unresolved symbol issues. Changes are made in a /src directory. I do a -dirclean, verify the package is removed from the /output/build directory. Then I make the package: the modified sources are copied to the /output/build directory to do the build. However, it seems buildroot is NOT using the modified .mk file in the build directory, as the changes made are not present on the Linker output line (i.e. still using the "old" link file list). I recall that buildroot seems to remember various names/symbols. So how do I "flush" this so that buildroot will use the new link file list?
When I manually edit the console output with the updated list, and execute in this in the build directory, it works just fine.
Thank you for your insights into this "weird" issue.
Related
I'm working on Unity with other people and there was a package installation problem while sharing the project. The package could be installed through url in the past, but it no longer supports url and only tgz files can be downloaded.
There was no problem installing the package, but a package installation error occurred when the project was run on another computer after sharing the project.
Looking at the error code, it was a problem with the path of the installed package. I included the tgz file in the project folder that I share and modified the absolute path of the package-lock.json file as the relative path. (Because each computer has a different project installation path.)
However, the modified path of the package-lock was changed back to the absolute path after the project was executed, so it was thought that the project could not be collaborated with this method.
What I'm curious about is that
Why does the path of the package-lock.json file change to the absolute path after executing unity?
Is there any other good way to share the package after installing it in the same situation as mine?
I cloned .NET 5 project, which should be working (unfortunately, I can't provide the project so you could reproduce the problem). I didn't change anything, I just wanted to build it, however, I am getting this error when restoring packages (although the project itself is on different disk, I found out that this is "global-packages" folder):
Could not find a part of the path 'C:\Users\me\.nuget\packages\microsoft.aspnetcore.azureappservices.siteextension\5.0.5\content\store\x64\net5.0\microsoft.extensions.configuration.environmentvariables\5.0.0\lib\netstandard2.0\Microsoft.Extensions.Configuration.EnvironmentVariables.dll'
However, I don't think it is a problem with this particular dll, as my colleague cloned the same project and he is getting the same error, but with different library.
This is what I've already tried doing:
Clearing all nuget cache
Checking "automatically check for missing packages during build in visual studio"
Updating everything I could (VS, nuget..)
Running VS as Administrator
Checking package sources (yes, nuget.org is there)
Adding "add key="repositoryPath" value="$..\..\packages"" into the nuget.config file - this didn't actually create the package folder in the defined path
Clean/rebuild/... everything
I think, that the problem will be in some setting, but I have no idea, where to look :/
Use the command dotnet restore
instead of
dotnet nuget
I'm trying to use the Node module react-tools provided by Facebook to compile my JSX files into their appropriate .js files.
jsx --extension jsx --no-cache-dir js/src js/build
However, using the supported command I'm not able to build files which are nested inside sub folders in my src folder.
I have js/src/module1/main.jsx
If I build this now, react-tools successfully builds
module("module1/main")
but then spews an error:
no such file of directory js/build/module1/main
However, if I make the directory js/build/module1 first, then I don't see any problems. It seems like react expects the output directory to already have the sub-directories in it. Am I doing something wrong here or is this a bug with react-tools at the moment?
Totally a bug in the main dependency of the jsx tool. :(
I filed https://github.com/reactjs/commoner/issues/67 to track.
Is there a script or a tool to generate the config.pri file for a BB10 project? Momentics IDE does it for you automatically whenever a project is refreshed or the directory is changed. Unfortunately, I am deploying and compiling via command line tools (it is an automated script which runs tests).
Without the config.pri file, I can't 'make'. An easy solution would be to track the file on github along with the source code for the project, but since the file has a timestamp on it, it causes many annoying merge conflicts.
Any ideas? I rather not write the script myself to parse through all the directories and accumulate header and source files myself. Since Momentics IDE does it, there must be a script that it calls or uses. Momentics is based off of Eclipse, is there any way to see what commands the IDE is calling?
config.pri is just an additional file included in the project's main .pro file. So if you're able to control .pro file you may not need config.pri at all and this inclusion could be safely removed from .pro file. For example, in earlier BB10 SDK releases config.pri simply didn't exist and has been added later.
.pro file is a main file for generating platform and environment-dependent Makefiles for building project, so I'm not sure if there's some tools allowing to manage it automatically. It could be initially generated by invoking qmake -project but I'm not sure if there are any console tools allowing you to manage it after automatically.
Technically, you should modify this file only if your project structure or build system options changed, all other stuff is done in platform-independent way.
I am compiling an app which is a sample app that uses an api. The api contains interface files (java files) and aidl files. Now I have problem in one of the interface file it cannot recognize the one of these aidl files exists in my project.
I have linked the whole api to the build path.
Does anyone has any idea ??
I had the same error, but it was fixed when I cleaned and rebuilded the project.
Projects -> clean project so it can automatically rebuild.
Look closely at your manifest file, check that the package etc are
spelled as you'd expect.
Also dont forget to paste the server's *.aidl and parcelable implementation (java) to your client project. These files has to have the same name and package as they were in the server project.
Here is some similar posts which might help:
ITelephony.aidl not compiling in eclipse
There are basically two possibilities.
(most likely) you need to make the folder that contains aidl files source folder. if you haven't done so, please do it.
You need a clean build.