Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Packages » Why each package should reside in its own directory?
Re: Why each package should reside in its own directory? [message #18305 is a reply to message #18304] Mon, 22 September 2008 00:23 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14258
Registered: November 2005
Ultimate Member
Novo wrote on Sun, 21 September 2008 16:37

luzr wrote on Sun, 21 September 2008 14:34


Also, sometimes when adopting 3rdparty sources, you can use approach demonstrated in plugin/png...

Mirek


In case of plugin/png and other plugins you copy files into plugin/<pakage> directory. I do not want to do that because I want to keep original source code structure, and I want that because I want to be able to update third-party source code from original VCS (CVS, SVN, Mercurial, Monotone, etc).



Why cannot your original source code structure start at package folder? (with U++ wrapper if needed).

Quote:


Another issue with UPP-project files is that project-files use absolute absolute paths. That makes impossible to move project files between computers and different OS.



Huh? The main purpose is to AVOID the need for absolute paths. All package file paths are package directory relative, UNLESS you use "Add any file" (which is only for the use in very specific situations).

Mirek
 
Read Message icon5.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: vsprintf() doesn't support "%I64u" format in Win32 platform?
Next Topic: Problem trying to run the example package OleCalc
Goto Forum:
  


Current Time: Tue May 13 21:19:38 CEST 2025

Total time taken to generate the page: 0.03803 seconds