View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000406 | Ecere SDK | compiler | public | 2010-04-21 00:10 | 2014-10-24 08:58 |
Reporter | redj | Assigned To | |||
Priority | high | Severity | feature | Reproducibility | N/A |
Status | new | Resolution | open | ||
Target Version | 0.46 eC II | ||||
Summary | 0000406: removing the need to use import "ecere" vs import static "ecere" depending on the linking method that was used | ||||
Description | make it happen! | ||||
Tags | No tags attached. | ||||
|
And what of linking ecereCOM or ecere statically as part of a dynamic library? How will we specificially tell the compiling tools to import only Ecere statically. |
|
I think if there static passed in the ide there is no point in having runtime shared dependencies as that is not what is intended. having the ability to have a statically linked .so file similar to ecere.dll might be useful though. |
Date Modified | Username | Field | Change |
---|---|---|---|
2010-04-21 00:10 | redj | New Issue | |
2010-05-03 22:23 | jerome | Note Added: 0000196 | |
2010-07-29 15:54 | jerome | Priority | normal => high |
2012-03-08 16:51 | redj | Target Version | => 0.45 Ginkakuji |
2012-03-29 07:50 | redj | Category | => eC Compiling Tools |
2012-03-29 07:50 | redj | Project | @2@ => Ecere SDK |
2014-07-11 18:53 | jerome | Target Version | 0.45 Ginkakuji => 0.46 eC II |
2014-10-24 08:47 | dardevelin | Note Added: 0001382 | |
2014-10-24 08:57 | jerome | Relationship added | has duplicate 0000632 |
2014-10-24 08:58 | jerome | Relationship added | related to 0000458 |