The problem is that I also have to load the dependencies (at least I think
I do), which is why I was trying to get to Mix programmatically.
On Thursday, February 15, 2018 at 4:29:48 PM UTC-6, Paul Schoenfelder wrote:
>
> I would second the boot loader approach when viable, but since it's not in
I would second the boot loader approach when viable, but since it's not in
your case, then there is nothing particularly special about how the paths
are set up, you just need to add the lib directory from your Elixir install
(e.g. `-pa /lib/*/ebin`). If you need to
compile the project as part of th
Oh, and just to clarify: I'm trying to do this in dev mode, so I want to
run the application from its project directory.
I may have to bit the bullet and just spawn a shell and run mix in it... :(
--
You received this message because you are subscribed to the Google Groups
"elixir-lang-core"
On Wednesday, February 14, 2018 at 4:25:36 PM UTC-6, José Valim wrote:
>
> We also do a similar setup in firenest test suite:
> https://github.com/phoenixframework/firenest/blob/master/test/shared/test.ex
>
>
I'm trying not to use a boot loader: the assumption is that the code for
the spawned n
I too would find this useful.
On Wednesday, February 14, 2018 at 2:19:04 PM UTC-5, pragdave wrote:
>
> ✓👍
>
> On Thursday, January 18, 2018 at 9:09:32 AM UTC-6, Ville Hellman wrote:
>>
>> Hey all,
>>
>> I'm proposing a new option for the `mix new` task: `--nocomments` when
>> run with this option
