I am trying to add a folder to the iso being built but anything I add to the iso folder location isn't included in the final iso.
My .bb do_install() installs the folder and files to ${iso} directory. And ls shows they are there in /iso in build/tmp. And i get no errors
Is there any documentation on Bitbake to add files to the iso root folder?
All i can find is adding to the Rootfs.
I guess you mean by ÌSO an ISO-Image. So i recommend you take a look at this part of the yocto mega manual. Something like
FILES_${PN} += "${bindir}/mydir1 ${bindir}/mydir2/myfile"
is needed to include installed files finally into the package ${PN}. Of course you have to install then the package into your image build.
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?
Using eclipse to create an Autotools-based project.
Starting from the "Hello World C++ Autotools Project" in the project creation wizard.
Here are the following steps.
Add a folder to the project called include.
Add a file to the include folder called Application.h.
Add #include <Application.h> entry into the src/proj.cpp file.
Trying to compile gets me a fatal error: Application.h: No such file or directory.
What is the autotools-fu I need to add my include folder to -I search path?
The Autotools plugin sorta follows the design of the GNU autoconf toolset, and so you need to configure the source files that are used by autoconf, automake, etc.
Start with the Autotools hello world project (I named mine AutoHello)
Project->New->Source folder->Folder name: include
Add the header file Application.h to the include folder. I just generated a new simple one, but you can copy an existing one too.
Add include/Makefile to the AC_CONFIG_FILES definition in configure.ac. (Note: *.ac files can be thought of as autoconf source files)
Add include to the SUBDIRS definition in Makefile.am (Note: *.am files can be thought of as automake source files)
Add a new file include/Makefile.am which will handle the automake behavior of the include folder.
Add a definition include_HEADERS to include/Makefile.am which lists all the headers contained in the folder. For this little example we simply list Application.h
In src/Makefile.am, add a definition a_out_CPPFLAGS. Give it a value of -I$(top_srcdir)/include. This tells our make target to add include as an include search path when compiling.
Project->Reconfigure Project
And that should give you a project that will compile a target that uses header files that are located in the include folder.
I have a Visual Studio 2015 solution with many projects. For one of the projects I would like the files from NuGet to download to a specific folder in my project. For example, I intend to use Bootstrap and also Signalr. I would like Bootstrap to download everything into one folder in my application, and not create folders within my project root. For example, I have a folder called 'Libs' in the project and would like those libraries to use 'Libs' as their root folder. This is due to an external build solution that handles everything in the 'Libs' folder.
I've found these docs about using a NuGet.config folder for the solution, but this does not handle my problem. Any ideas?
As far as I'm aware, this isn't possible. Each Nuget package is written with specific instructions on how to install into a project. One of those instructions is where to put files, another example would be what transform to apply to the web.config. Nuget doesn't specify a way to modify these instructions. The only thing you could do would be to modify the packages yourself - download the .nupkg file and open it up as a zip file, you will be able to edit the folder structure from there.
I cab export my plugin manually as a folder and I can set option to unpack *.jar after installation from Update Site. But how can I totally avoid using *.jar archives? Is there a way to build Update Site for my plugin with a folder with its contents except *jar archive?
If you use 'features' to build your update site you can specify the 'unpack the plug-in archive after the installation' option in the feature.xml.
However I think this will still loose any execution bit set on files.
Update:
The 'build.properties' file in a feature can specify additional files to put in the root or other directories. You can specify the permissions for these files:
root=file:filename
root.permissions.755=filename
See the Root file Properties help
I developed a tool that besides DLL requires a strong named folder with 2 files in solution. Using NuGet GUI I created the folder and populated with files, but when I install package, the only DLL created but folder with 2 files are not. How can that be fixed?
NuGet has a set of conventions that define certain folders inside the NuGet package that will result in different actions being taken when the package is installed or uninstalled.
In order for folders to be created inside the project, when the NuGet package is installed, the folders need to be inside a Content directory. If you look at the jQuery package, it has a Content\Scripts folder with files inside it. This Scripts folder will be created inside your project, along with its files, when you install the jQuery NuGet package.
\Content
\Scripts
\jquery-2.1.0.js