Several packages and buildsystems (most notably cmake) badly trip
over CC="ccache gcc" so create local wrapper scripts in the build
dir and set CC/CXX to them to work around that - like we do for
host-gcc and gcc in toolchain.
Signed-off-by: Matthias Reichl <hias@horus.com>
fixup scripts/build local-cc wrapper
* Switch: it builds
* Switch: Use udev to finalize usb gadget to save from systemd looping service restart until cable connected.
* Switch: Update kernel stuff again
* Switch: Downgrade Alsa packages to version in 4.x tree
* Joycond: Update Switch version
* Switch: Minor fixes
* LibreELEC: Fix a few broken files from upstream pull
* Switch: Fix LibreELEC build.
* Switch: Update bootloader stuff
* L4T: FFMPEG: Add support for nvv4l2 decoder/encoder
* FFMPEG: Add back encoder support for game recording in retroarch
* FFMPEG: revert a few changes, and add support for vulkan.
Timing detail reporting can be enabled by setting
TRACE_BUILD_TIMING=1
This enables timestamping collecting at various build stages so we
can easily analyze how long eg configure, make/build, install etc
steps take.
Signed-off-by: Matthias Reichl <hias@horus.com>
add flag "-o" to overwrite file on unzipping.
when a build is interrupted by some issues, it will cause a re-substitution problem after a rebuild the target whose source code come from a zip file (like target jzintv)
* Initial fully buildable/bootable Odin Support
* Rework NX-Boot to FAT32 Boot for shared usage between switch and odin
* Move shared packages from switch/odin to main packages folder
* orangepi-4-lts: rename orangepi-lts -> orangepi-4-lts
* orangepi-4-lts: split makefile and dts patches, update dts patch from armbian and remove sections that don't build
Specifically:
```
&i2s0 {
assigned-clocks = <&cru SCLK_I2SOUT_SRC>;
assigned-clock-parents = <&cru SCLK_I2S0_8CH>;
resets = <&cru SRST_I2S0_8CH>, <&cru SRST_H_I2S0_8CH>;
reset-names = "reset-m", "reset-h";
rockchip,playback-channels = <2>;
rockchip,capture-channels = <2>;
status = "okay";
#sound-dai-cells = <0>;
};
```
and
```
&hdmi_in_vopl {
status = "disable";
};
```
result in a syntax error for some reason I don't understand, which likely means no sound for now
The buildsystem's Makefile hardcodes the location of the BUILD_DIR used
by the rest of the buildsystem. Add a script to handle what BUILD_DIR
might be set to.
Signed-off-by: Ian Leonard <antonlacon@gmail.com>
* Downgrade glibc to 2.27 for L4T Builds.
* Downgrade binutils to 2.32 for L4T Builds.
* Update L4T Project Options
* Refactor tegra-bsp package
* Import/Rebase CTC's ffmpeg patches, and switch decoder to nvv4l2 from nvmpi. Fixes decoder issues
* Enable all disabled cores
* Remove hack in busybox package to dump firmware into L4T Builds, we now handle this in tegra-bsp package.
* More L4T project cleanups
* Bring switch-bootloader package.mk inline with upstream formatting
* Fix reboot_payload
* Add proper tegra-bsp:init support
* Bootloader cleanups, seperate bootloader stuff for libreelec builds
* Update init for supporting all distros on Nintendo Switch
* Add proper splash images for libreelec builds.
* Final bootloader fixes
* switch-bootloader-merge-fixes
* Fix uboot merge issues
* fix bmp
* It all builds
* add Basic USB Gadget(Serial console only)
* Properly fix mtp, and finish gadget stuff
In case SYSTEM_SIZE was higher than 1024, mcopy would fail without the
failure being caught. The failure was probably due to invalid geometry
(number of sectors per track too high?). However mformat should be able
to determine the geometry on its own, when no geometry parameters are
supplied. After discussion on IRC with vpeter we came to this solution.
* create temporary folder in the target folder
* use sparse files to create image and partitions
* no extractions of the partitions from image
* modify mcopy alias to copy to the partition sparse file
* add `-o` switch to mcopy alias, so mcopy does not prompt in case of
existing file in the partition
* remove alias for mformat (is used only one time)
* catch errors for mformat/mcopy/mmd
* use mcopy alias when copying files to virtual appliance part1
* move DISK_LABEL setting closer to the part where it is used
* write MBR without test (it should be already present and if not, dd
will fail anyway and error is caught)
* update output when vmdk is created
Co-authored-by: Peter <peter.vicman@gmail.com>
preserves space, tarballs can be reused if the package repository gets
nuked or the commit disappears from the history (e.g. in case of a
forced pushed)
