Home » Developing U++ » U++ Developers corner » Include option for specific package
|
|
|
|
| Re: Include option for specific package [message #22208 is a reply to message #22203] |
Wed, 24 June 2009 13:28   |
|
|
I agree with Koldo!
Maybe I proposed not finished variant. but we can restrict for do not permit to set absolute paths
| koldo wrote on Wed, 24 June 2009 11:59 |
Hello mr_ped
Nobody in this thread wants absolute paths 
| mr_ped wrote on Wed, 24 June 2009 10:09 |
| luzr wrote on Tue, 23 June 2009 17:09 |
Well, I am sorry to be stubborn, I am just STRONGLY opposed to the idea that package should have any explicit include paths.
Mirek
|
+1
That would make packages hard to relocate easily, like now.
|
We only want paths relative to package folder and under it.
For example, this diagram:
Why this. For making wrappers to other libraries.
Situations:
1. Library directory structure is very simple: Nothing to do
2. Library directory structure is not very simple. Solutions:
2.1 Change library source code. In my opinion this is ugly
2.2 Put the library tree under Upp package and compile it seting include path structure under Upp package. This is something we like.
Best regards
Koldo
|
|
|
|
|
|
|
| Re: Include option for specific package [message #22221 is a reply to message #22216] |
Thu, 25 June 2009 13:20 |
|
|
Thank you Mirek, Sorry us for the resistance too!
If you have not time for this, I can propose the final variant to restrict access for any path, and integrate FileSel to select folder.
With respect, Ion Lupascu (tojocky)
| luzr wrote on Wed, 24 June 2009 20:38 |
Well, OK, sorry for the resistance.
I have tried, my proposal, although solving the problem, is rejected.
I will add tojocky's method ASAP.
The only thing to consider is some better name that would indicate that the whole issue is really only useful for incorporating 3rd party libraries....
Mirek
|
|
|
|
|
|
|
| Re: Include option for specific package [message #22276 is a reply to message #22266] |
Mon, 29 June 2009 14:49 |
|
|
| luzr wrote on Sun, 28 June 2009 22:53 |
Done.
|
Hello Mirek,
Nice realization, but..... my realization it adds internal include package for current build package and for uses packages. In your realization add internal include package only fro current build package.
I want to discuss about this, how is correct. Your realization is good when I do a package which wrap a library.
In my case (XLSLIB) it is not work because I use direct link to library from other package!
OK, Question:
Is correct to add include package for uses packages too?
My opinion: it is necessary to add (by priority) inlcude internal package for uses packages.
[Updated on: Mon, 29 June 2009 15:06] Report message to a moderator |
|
|
|
|
|
|
|
| Re: Include option for specific package [message #22285 is a reply to message #22279] |
Tue, 30 June 2009 16:42 |
|
|
| luzr wrote on Mon, 29 June 2009 20:56 |
Changed: All packages now using internal include paths.
Mirek
|
Hello Mirek!
It is better, but analyzing package structure, for example:
If only XLS Lib package have internal include then on building need add only for: XLS_LIB and Current_Package.
For other packages as CtrlLib, CtrlCore, and other is not need to add!
-
Attachment: upp_tree.PNG
(Size: 17.26KB, Downloaded 455 times)
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Sat Apr 27 10:50:51 CEST 2024
Total time taken to generate the page: 0.03307 seconds
|
Members
Pages
Help
Register
Login
Home
