summaryrefslogtreecommitdiffstats
path: root/scripts/upload.sh
Commit message (Collapse)AuthorAgeFilesLines
* Add generic qemuarmv7 machine configSamuli Piippo2017-10-021-0/+1
| | | | | | | | To be used in Qt CI builds Task-number: QTQAINFRA-1457 Change-Id: I7ef21aa05c65f50539e2f70b21da375a9b3eea02 Reviewed-by: Sami Nurmenniemi <sami.nurmenniemi@qt.io>
* Remove all *.ci.local network addressesSamuli Piippo2017-08-111-1/+1
| | | | | | | | | The dot-local addresses cause problems with mDNS lookups, replace all with *.intra.qt.io aliases that are now available. Task-number: QTBUG-60153 Change-Id: I60e2e06440ca088d1194615849bf7792c16df362 Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
* Use actual Qt version for upload locationSamuli Piippo2017-06-191-1/+1
| | | | | Change-Id: I7629bcba7aadf9acb417d2c0b3567e1a0e9e69eb Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
* Change upload location to 5.9Samuli Piippo2017-01-261-1/+1
| | | | | Change-Id: I327e03b25c813dc67172bc57f94dc1ce3c1cecea Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
* Add support for creating QBSP packageSamuli Piippo2016-11-211-24/+10
| | | | | | | | | | | | | | | | | | | | | | | | QBSP is a Qt specific Board Support Package that can be installed with the Qt SDK or MaintenanceTool and contains a system image and a toolchain. The toolchain is automatically registered to the QtCreator. The recipes used for creating the system image and the toolchain can be configured with QBSP_IMAGE_TASK and QBSP_SDK_TASK. The files wanted for the system image can be further configured with QBSP_IMAGE_CONTENT, with a list of files located in DEPLOY_DIR_IMAGE folder. By default, .img and .conf files are used from the selected image recipe. QBSP_INSTALLER_COMPONENT defines the location in the Qt installer tree where the QBSP is shown and QBSP_VERSION defines the version for the components. The QBSP is installed to path defined by QBSP_INSTALL_PATH. The regular SDK creation can now reuse the same image package .7z, so update upload script to use it instead of creating new package. Task-number: QTBUG-57018 Change-Id: Id1e7cc4ab3998a7d450f23ed603b8e676b314d63 Reviewed-by: Iikka Eklund <iikka.eklund@qt.io> Reviewed-by: Teemu Holappa <teemu.holappa@qt.io>
* tegra: update to latest vibrante pdkSamuli Piippo2016-11-141-1/+1
| | | | | | | | | | [RC 2.5] 25.11.01 Vibrante 4.0 Linux Drive CX2 - PDK Drop support for nvidia-logan Change-Id: I9b2c55f213ff3eb01969a49ad64e596692fcee31 Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io> Reviewed-by: Teemu Holappa <teemu.holappa@qt.io>
* Revert "tegra: update to latest vibrante pdk"Samuli Piippo2016-10-141-1/+1
| | | | | | | | | Problems with eglfs, so revert back to previous PDK. This reverts commit 323408406d9133a5462a24fea4ec86e649088180. Change-Id: I3ee36809cb823aefdc03f8a24d052c2a76f308db Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* tegra: update to latest vibrante pdkSamuli Piippo2016-10-061-1/+1
| | | | | | | | | [RC 2.5] 25.11.01 Vibrante 4.0 Linux Drive CX2 - PDK Drop support for nvidia-logan Change-Id: Ic8c76313704c3e666050284f02cb1a40237366e5 Reviewed-by: Risto Avila <risto.avila@qt.io>
* Upload content to 5.8 folderSamuli Piippo2016-06-081-1/+1
| | | | | Change-Id: I21f74c3f0c98dffbc1ad5329f903b95e800d8304 Reviewed-by: Kimmo Ollila <kimmo.ollila@theqtcompany.com>
* Update license headersSamuli Piippo2016-05-181-7/+15
| | | | | | | License changed to GPLv3 + Commercial Change-Id: I267c97216e717ed29071df064337e1bcf83de973 Reviewed-by: Kalle Viironen <kalle.viironen@theqtcompany.com>
* Fix to NVidia's tegra configurations.Teemu Holappa2016-05-051-2/+3
| | | | | | | | | | | | | | Changed both nvidia-logan and tegra-t18x to use the same metalayer from the Vibrante 4.0 SDK. Kernel sources and libraries are stored into the internal CI repository. These definitions can be overridden by SDK folder using following environment variables: export KERN_DIR=~/Vibrante4.0_RC1/vibrante-t186ref-linux_src/kernel export PLATFORM_TOPDIR=~/Vibrante4.0_RC1/vibrante-t186ref-linux export TOOLCHAIN_PATH=~/Vibrante4.0_RC1/toolchains/tegra-4.9-nv export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE TOOLCHAIN_PATH KERN_DIR PLATFORM_TOPDIR" Change-Id: If58a0fcbe01daa9a55dd041b79a9d80a90fde284 Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
* nvidia-t18x supportLouai Al-Khanji2016-03-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Steps to use this: Set up vibrante installation, mine looks like this: $ ls -l ~/VibranteSDK total 234880 drwxrwxr-x 1 louai louai 298 Mar 20 2014 eclipse -r-xr-xr-x 1 louai louai 171826846 Jan 4 09:59 NVIDIA_Tegra_Graphics_Debugger_2.1_linux-v4l_l4t-egl.run -r--r--r-- 1 louai louai 68688729 Jan 4 09:59 NVIDIA_Tegra_System_Profiler_2.5-linux-x64.tar.gz drwxr-xr-x 1 louai louai 262 Jan 5 14:50 toolchains drwxrwxr-x 1 louai louai 34 Jan 5 13:55 vibrante-oss-src drwxr-xr-x 1 louai louai 12 Jan 4 09:47 vibrante-t186ref-cuda drwxrwxr-x 1 louai louai 264 Feb 10 10:50 vibrante-t186ref-foundation drwxr-xr-x 1 louai louai 164 Jan 5 14:49 vibrante-t186ref-foundation_src drwxrwxr-x 1 louai louai 228 Jan 5 13:56 vibrante-t186ref-linux drwxr-xr-x 1 louai louai 314 Feb 10 10:58 vibrante-t186ref-linux_sr Set up Yocto build dir: $ mkdir ~/work $ cd ~/work $ ~/tqtc-b2qt/yocto-meta/b2qt-init-build-env init --device tegra-t18x Add NVIDIA's Yocto things: $ mkdir ~/work/sources/nvidia-layer $ cd ~/work/sources/nvidia-layer $ tar xf ~/VibranteSDK/vibrante-t186ref-linux_src/yocto/nvidia-layer.tgz $ cd - Set up build environment: $ export MACHINE=tegra-t18x $ . setup-environment.sh Set the following environment variables: $ export KERN_DIR=~/VibranteSDK/vibrante-t186ref-linux_src/kernel $ export PLATFORM_TOPDIR=~/VibranteSDK/vibrante-t186ref-linux $ export TOOLCHAIN_PATH=~/VibranteSDK/toolchains/tegra-4.9-nv $ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE TOOLCHAIN_PATH KERN_DIR PLATFORM_TOPDIR" Add NVLAYER_DIR to local.conf: $ echo 'NVLAYER_DIR = "${TOPDIR}/../sources/nvidia-layer"' >> conf/local.conf Build your image: $ bitbake b2qt-embedded-qt5-image Flash your board: $ cd $PLATFORM_TOPDIR $ mv targetfs targetfs-old $ cd targetfs && tar xf /path/to/rootfs.tar.bz2 $ cd ../../vibrante-t186ref-foundation/utils/scripts/bootburn $ ./bootburn.sh -b p2382-t186 Change-Id: I4209cd0c19a007c4457460fd67342fc579c2a735 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Deploy build artifacts to 5.7 folderSamuli Piippo2016-03-171-1/+1
| | | | | Change-Id: Icf6e9610d26aa4c073b49655d691570ba099f5ff Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Update license headersSamuli Piippo2016-02-091-14/+13
| | | | | Change-Id: Iabcf736e6f4ae2149b57c84ebdc8b5b1be82023d Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Upload mingw32 toolchainSamuli Piippo2016-02-051-6/+3
| | | | | | Change-Id: I993eed21313dc91daa46197d9d19363a839953ce Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com> Reviewed-by: David Schulz <david.schulz@theqtcompany.com>
* Rename toolchain output fileSamuli Piippo2015-12-291-1/+3
| | | | | | | | | Rename the toolchain output to use both SDKMACHINE and MACHINE in the name, so that we don't need to rename it when uploading. This also adds -mingw32 into the windows SDK name. Change-Id: Id70c8bc456a15d263579eefdaa2a0e136741d0ba Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Package and upload nvidia-logan imageSamuli Piippo2015-12-151-3/+11
| | | | | Change-Id: Ifc290c4a6510aa4d7cd03eec944a7428f97e66a2 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Upload only qt5 image and toolchainSamuli Piippo2015-12-091-36/+11
| | | | | | | The old non-qt image and toolchain are no longer used. Change-Id: I9416d29af5b505810744cb4cbce0e99415a90566 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Package image and config before uploadingSamuli Piippo2015-12-081-2/+4
| | | | | Change-Id: I65370af9b9d1f7362a6e5ad66dc124909835efd2 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Create separate automotive SDKSamuli Piippo2015-12-081-1/+1
| | | | | | | | | Automotive toolchain will contain packages that are not available in the B2Qt embedded toolchain. Add empty packagegroup recipe that can be used to add new content to automotive sdk. Change-Id: I43c520db9b4f292226b2b5402bb460232a20ede3 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Generate deploy conf for flashing wizardSamuli Piippo2015-12-021-0/+2
| | | | | | Change-Id: I23cc54e51b7d10db0fd64d6676bd86cdf029beda Reviewed-by: Rainer Keller <rainer.keller@theqtcompany.com> Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Create .img binary image for all devicesSamuli Piippo2015-12-011-8/+4
| | | | | | | | | Use the sdcard bbclass from meta-fsl-arm to build binary image for TI hardware. Append all other image creation functions to create the .img symlink. Change-Id: I1bb0b5ea893789831d6fae27ece93ce238bfcb49 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* upload automotive emulator imageSamuli Piippo2015-11-301-2/+4
| | | | | Change-Id: Ie3e051234d5c75170931cc3613452eadd6e1973c Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Upload NUC image (.hddimg)Samuli Piippo2015-11-271-0/+2
| | | | | Change-Id: Ib589e4ac6951add1de7c9c901eb180b012e7786a Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* upload automotive toolchain and imageSamuli Piippo2015-11-261-0/+8
| | | | | Change-Id: If7a925c688c99d3af1f864c24b187df2beacf709 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* script: rework the upload scriptSamuli Piippo2015-11-201-20/+7
| | | | | | | | Rename qt5 binary images to .img and qt5 toolchains to b2qt-x86_64-qt5-toolchain-${MACHINE}.sh Change-Id: I8972a82dc1b57f83f2b50cf89fd0dbe9f8cf634f Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Create and upload binary imagesSamuli Piippo2015-11-171-0/+15
| | | | | | | Binary images created for imx6 and RPi devices, upload also for nuc. Change-Id: I4e7533965a6b04a5665ef237acf198b7c867d3f6 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* scripts: upload qt5 image and toolchainSamuli Piippo2015-10-291-0/+8
| | | | | Change-Id: Iaf134c0d4ef5d091a2c6f62904550f282a9a02b3 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Set upload path to 5.6 releaseSamuli Piippo2015-08-191-1/+1
| | | | | Change-Id: I59efd1d9e6912e43a343cd3e9d56f54166209fcc Reviewed-by: aavit <eirik.aavitsland@theqtcompany.com>
* No renaming for nitrogen6x anymoreSamuli Piippo2015-06-091-5/+1
| | | | | Change-Id: I55cad9b2a0a418bd034e2c56d575164a5ccf4922 Reviewed-by: Eirik Aavitsland <eirik.aavitsland@theqtcompany.com>
* scripts: changes on upload scriptSamuli Piippo2015-02-191-6/+6
| | | | | | | Change the upload location, eglibc was changed to glibc. Change-Id: I080b2af14981d84cdd7f3d3765e56cf33a2d2695 Reviewed-by: Andy Nichols <andy.nichols@theqtcompany.com>
* Script to upload machine images and toolchainsSamuli Piippo2014-11-241-0/+52
upload.sh can be used to upload machine images and toolchain to ci-files02-hki, which is used by the b2qt build scripts. It also does some necessary renaming and the special handing for Freescale SABRE board boot package. Change-Id: I73a0873669a5e5a7929ec27cb929e29616def8cf Reviewed-by: Laszlo Agocs <laszlo.agocs@theqtcompany.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-20 21:13:51 +0000