Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 52 of 52 FirstFirst ... 242505152
Results 766 to 774 of 774

Thread: Build my own Vix image

  1. #766

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    726
    Thanks
    62
    Thanked 242 Times in 167 Posts
    Quote Originally Posted by twol View Post
    So that 5.5.1 branch is missing some important changes…Developer should be fine……what did it fail with?
    I don't remember, I'll try a dev build again

  2. #767
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,975
    Thanks
    245
    Thanked 1,689 Times in 1,332 Posts
    Quote Originally Posted by lincsat View Post
    I don't remember, I'll try a dev build again
    A dev build worked for me for an et80000. Just checked out out the 5.5.1 branch of OE-A and then ran a build. (No patches required).
    Although looking at what my front-end script would have set for DISTRO_TYPE - it would have left it blank (things must have changed in the last few years).

    From what i can see of the meta-oe-alliance/meta-oe/conf/distro/openvix.conf file it checks for DISTRO_TYPE being release - anything else is taken as developer.
    Last edited by birdman; 06-01-25 at 02:57.
    Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  3. #768

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    726
    Thanks
    62
    Thanked 242 Times in 167 Posts
    OK, I've now had a vuultimo4k build succeed on the 5.5.1 branch. I currently have a ZGemma build going but have discovered that I had managed to use Developer (upper case D) rather than developer (lower case d) that I had been using, so it's building into a different folder. I'll correct that here and should be cooking again.

  4. #769
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    14,155
    Thanks
    2,078
    Thanked 5,233 Times in 3,456 Posts
    Quote Originally Posted by birdman View Post
    A dev build worked for me for an et80000. Just checked out out the 5.5.1 branch of OE-A and then ran a build. (No patches required).
    Although looking at what my front-end script would have set for DISTRO_TYPE - it would have left it blank (things must have changed in the last few years).

    From what i can see of the meta-oe-alliance/meta-oe/conf/distro/openvix.conf file it checks for DISTRO_TYPE being release - anything else is taken as developer.
    No idea what you mean by this. DISTRO_TYPE is set on the command line.

    Code:
    ENIGMA2_URI ?=
    And that is just the default. Anyone with their own repo overrides that in site.conf.
    Help keep OpenViX servers online.Please donate!

  5. #770
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,975
    Thanks
    245
    Thanked 1,689 Times in 1,332 Posts
    Quote Originally Posted by Huevos View Post
    No idea what you mean by this. DISTRO_TYPE is set on the command line.
    Sorry, so it is. I didn't read that far down.

    Doesn't alter the fact that openvix.conf only checks for it being "release" and treats anything else as developer, e.g.

    Code:
    IMAGE_BUILD = "${@bb.utils.contains("DISTRO_TYPE`", "release", "${BUILD_VERSION}" , "${BUILD_VERSION}.${DEVELOPER_BUILD_VERSION}", d)}"
    Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  6. #771
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    14,155
    Thanks
    2,078
    Thanked 5,233 Times in 3,456 Posts
    Quote Originally Posted by birdman View Post
    Sorry, so it is. I didn't read that far down.

    Doesn't alter the fact that openvix.conf only checks for it being "release" and treats anything else as developer, e.g.

    Code:
    IMAGE_BUILD = "${@bb.utils.contains("DISTRO_TYPE`", "release", "${BUILD_VERSION}" , "${BUILD_VERSION}.${DEVELOPER_BUILD_VERSION}", d)}"
    Officially we only build 2 images, Release and Developer, so why would we have more than 2 options? Anyone who is building something other than the official 2 can feed in whatever values they choose.
    Help keep OpenViX servers online.Please donate!

  7. #772
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,975
    Thanks
    245
    Thanked 1,689 Times in 1,332 Posts
    Quote Originally Posted by Huevos View Post
    Officially we only build 2 images, Release and Developer, so why would we have more than 2 options?
    The comment was in response to:

    I have built a vuultimo4k 6.7.000.007 image on the 5.5.1 branch using DISTRO_TYPE=Developer-OE-A-branch-5-5-1 make image but just using Developer fails.
    Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  8. #773
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    14,155
    Thanks
    2,078
    Thanked 5,233 Times in 3,456 Posts
    Quote Originally Posted by birdman View Post
    The comment was in response to:
    I have no clue what that is. That was a temporary feature branch. And adding that as DISTRO_TYPE is clearly wrong. Currently 5.5.1 uses Dev branch, and 5.5 uses an old archived branch.
    Help keep OpenViX servers online.Please donate!

  9. #774

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    726
    Thanks
    62
    Thanked 242 Times in 167 Posts
    At last I've figured out my problem with building on Ubuntu 24.04 LTS - the upgrade from 22.04 had broken NordVPN, as soon as I removed and reinstalled that, the builds started working properly again.

Page 52 of 52 FirstFirst ... 242505152

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.