Recent

Author Topic: When to create packages?  (Read 3395 times)

wimpie

  • New Member
  • *
  • Posts: 32
When to create packages?
« on: August 13, 2009, 05:48:27 pm »
Hi

I have a component that I want to distribute. It is non-visual and can't be put on the GUI (like TTimer can). Should I make a package for it? Why, what is the advantages / uses of the package if it can't be installed into the IDE

If I need to make a package, what goes in there apart from the units? For example, should the license file, readme etc also go in? When should a lot of stuff go into one package and when should it be split into multiple packages?

It's a lot of questions but I have spent many hours on the website and can't get clarity about this. Unless of course I never found THE source for this info.

Thanks for any responses.

theo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1891
Re: When to create packages?
« Reply #1 on: August 13, 2009, 06:06:53 pm »
Why, what is the advantages / uses of the package if it can't be installed into the IDE
The user of your package doesn't have to fiddle with paths but can simply add the dependency of your package to his project. A package can have its own compiler settings etc.

wimpie

  • New Member
  • *
  • Posts: 32
Re: When to create packages?
« Reply #2 on: August 14, 2009, 09:08:40 am »
Thanks. That's a good reason to make packages.

 

TinyPortal © 2005-2018