Not sure what’s going on, mix compile shows my deps warnings.
smathy
dimitarvp
smathy
Right, but that doesn’t differentiate its behavior from what it does on your own code, you’ll only see warnings if it’s actually compiling that too.
0
Onor.io
Hmm. mix compile doesn’t show me dependency warnings. It shouldn’t need to recompile dependencies for a mix compile–not normally anyway.
1
smathy
Like you blow away your _build directory, and mix compile doesn’t show dependency warnings as it’s compiling them?
0
Onor.io
I don’t usually blow away my _build between mix compile cycles. To me that’d be more along the lines of a “clean then compile.”
1
LostKobrakai
That’s only the case if the dependencies have been compiled before. Depending on the project and workflow that might not always be the case. E.g. at work we maintain a bunch of mix projects, many libraries, so almost all changes (and therefore switching between branches) changes dependencies and therefore their compiled status.
1
Onor.io
I guess then it would depend on how frequently one needs to switch sets of dependencies. The projects I’ve worked on have always tended to be conservative on adding and updating external packages.
1
smathy
Right, obviously. Anyway, yes, your main point is correct, if OP is explicitly running deps.compile then they’ll be seeing all their deps warnings because apparently that forces a compile even if the deps are already compiled.
1
Onor.io
I guess my point here would be that the behavior of mix deps.compile and mix compile can be different and hence one can see different sets of warnings. mix compile (provided that the packages were already compiled) should only show warnings on my code–not warnings on dependencies. But, as you say, it would depend on exactly what needs to be built.
0