Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Toolchain re-org #919

Closed
tonytheodore opened this Issue Oct 11, 2015 · 13 comments

Comments

Projects
None yet
3 participants
@ooxi

This comment has been minimized.

Copy link
Contributor

ooxi commented Oct 11, 2015

I'll be glad to give you a helping hand, is there anything I can do to support this issue? :)

@starius

This comment has been minimized.

Copy link
Member

starius commented Oct 12, 2015

Can src/cmake/modules path (or it's installed copy in usr/) be included in the package mxe-conf?

@tonytheodore

This comment has been minimized.

Copy link
Member Author

tonytheodore commented Oct 12, 2015

It could be installed by mxe-conf, it would work and even git wouldn't notice that we installed it multiple times. This may be the best short-term solution to #918 though we still need do get the rest right.

As an aside, I'd lean towards including all mxe sources for reference (and possibly as a legal requirement of changes made).

@ooxi

This comment has been minimized.

Copy link
Contributor

ooxi commented Oct 12, 2015

I strongly agree with installing the mxe sources from which the binary packages were build. This would also eliminate possible incompatibilities between new commits and existing binary packages.

@starius

This comment has been minimized.

Copy link
Member

starius commented Oct 12, 2015

I'm going to add new common package mxe-src to build-pkg, which includes src directory. All other packages depend on mxe-src as well as on mxe-requirements.

possibly as a legal requirement of changes made

I have overlooked this issue. GPL'ed packages require distributing source along with binary packages. Is it worth adding package mxe-pkg with directory pkg?

@tonytheodore

This comment has been minimized.

Copy link
Member Author

tonytheodore commented Oct 12, 2015

GPL'ed packages require distributing source along with binary packages

IANAL, but I believe you only need to make the sources available on request. Otherwise, no modern OS could ship on (say) a CD.

Is it worth adding package mxe-pkg with directory pkg?

I would say no, especially not as a requirement. Maybe as a recommends package, but no other normal debian packages do that.

Updated: Probably a deb-src in apt sources would be sufficient.

@starius

This comment has been minimized.

Copy link
Member

starius commented Oct 12, 2015

AFAIK deb-src is what binary packages are built from. You can say apt-get source mxe && cd mxe* && debuild and it build all binary packages for you.

@tonytheodore

This comment has been minimized.

Copy link
Member Author

tonytheodore commented Oct 13, 2015

Can src/cmake/modules path (or it's installed copy in usr/) be included in the package mxe-conf?

@starius, indeed, having the native mxe-conf install these modules in usr/ is a very good idea that I've included in the pull request. (Installing the mxe sources is mostly orthogonal to this).

I'll be glad to give you a helping hand, is there anything I can do to support this issue? :)

@ooxi, test out #925 and see if it behaves as expected.

@ooxi

This comment has been minimized.

Copy link
Contributor

ooxi commented Oct 13, 2015

@ooxi, test out #925 and see if it behaves as expected.

By running make with your patches?

@tonytheodore

This comment has been minimized.

Copy link
Member Author

tonytheodore commented Oct 14, 2015

Yes, though it takes a looong time to build. Probably better to keep testing the apt packages unless you have lots of cycles to spare.

tonytheodore added a commit to tonytheodore/mxe that referenced this issue Oct 19, 2015

update build-pkg.lua for toolchain re-org
1. Remove common packages.

  Common packages served a replacement for native target.
  Now we have native target and don't need common packages.
  Existing common files (ncurses) have to be fixed.

2. Package -> Item.

  Item means a string "target~package".
  All functions which used packages now use items.

3. One build list instead of 4 build lists.

  All items are sorted and built together without separation
  by target.

4. No module-global variable "target".

  All functions using target now get "item" and target is
  extracted from item. All remaining module-global variables
  don't change (are constants) or are created in the bottom
  of the module.

5. MXE_MAX_PACKAGES -> MXE_MAX_ITEMS

see mxe#925
see mxe#919

tonytheodore added a commit to tonytheodore/mxe that referenced this issue Oct 22, 2015

update build-pkg.lua for toolchain re-org
1. Remove common packages.

  Common packages served a replacement for native target.
  Now we have native target and don't need common packages.
  Existing common files (ncurses) have to be fixed.

2. Package -> Item.

  Item means a string "target~package".
  All functions which used packages now use items.

3. One build list instead of 4 build lists.

  All items are sorted and built together without separation
  by target.

4. No module-global variable "target".

  All functions using target now get "item" and target is
  extracted from item. All remaining module-global variables
  don't change (are constants) or are created in the bottom
  of the module.

5. MXE_MAX_PACKAGES -> MXE_MAX_ITEMS

see mxe#925
see mxe#919

tonytheodore added a commit to tonytheodore/mxe that referenced this issue Oct 25, 2015

update build-pkg.lua for toolchain re-org
1. Remove common packages.

  Common packages served a replacement for native target.
  Now we have native target and don't need common packages.
  Existing common files (ncurses) have to be fixed.

2. Package -> Item.

  Item means a string "target~package".
  All functions which used packages now use items.

3. One build list instead of 4 build lists.

  All items are sorted and built together without separation
  by target.

4. No module-global variable "target".

  All functions using target now get "item" and target is
  extracted from item. All remaining module-global variables
  don't change (are constants) or are created in the bottom
  of the module.

5. MXE_MAX_PACKAGES -> MXE_MAX_ITEMS

see mxe#925
see mxe#919
@ooxi

This comment has been minimized.

Copy link
Contributor

ooxi commented Oct 26, 2015

How much disk space does make require? I've run out of disk with a 10 GiB image (now retrying with 50 GB).

@starius

This comment has been minimized.

Copy link
Member

starius commented Oct 26, 2015

I build with build-pkg.lua and get the following sizes:

9.1G    usr/.git/
39G     usr/
2.1G    pkg/
1.2G    log/
55G     .

Top directory is about 13G because of tarballs and Debian packages.

If you build with make, you could get about 35G.

@ooxi

This comment has been minimized.

Copy link
Contributor

ooxi commented Oct 28, 2015

make 03a941b succeeded :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.