I have published a fix for this issue at
http://erlide.org/update_nightly. You will have to reconfigure your
projects, unfortunately. I hope you can copy and paste the values
between projects. Detecting and importing old settings would take more
time to implement, if you really want to do that, please let me know.
Please note that if you declare custom options that are handled
separately (like warnings or parse transform), they will be ignored,
i.e. the fields above are overriding these values.
Please let me know if it works for you.
Thanks for reporting the problem!
On Tue, Jun 19, 2012 at 11:30 AM, Vlad Dumitrescu <vladdu55@...> wrote:
> On Tue, Jun 19, 2012 at 10:20 AM, Łukasz Kubica
> <Lukasz.Kubica@...> wrote:
>> You have removed custom compiler options in recent version. This is
>> ridiculous to remove such things. Without this erlide is quite unusable in a
>> real-life project, beacause i cannot reference another project and use
>> -icnlude_lib from it (even if i could, i still have external libraries which
>> I do not want to compile yet i need -include_lib from them. So I even cannot
>> reconfigure all my 50+ projects. Thank you.
> Yes, you are right, it wasn't a good idea to remove that completely. I
> am sorry that I caused you trouble. To my defense, it is planned to
> implement a different way to do that, but I got sidetracked.
> I think the fastest way to get a fix is if I put back the custom
> options box. I will try to do that today, but you will have to use a
> nightly build to get it, I hope that is ok. Until then, you can revert
> to an older version of erlide.
> On a sidenote, one of the reasons why the version numbers are still
> 0.x (i.e. not final releases) is that we can do such radical things if
> needed. We try not to, but sometimes it may be required.
> best regards,