My long term goal is to contribute functionality to Testcafe. Immediately, I'm trying to include it in my current node project so that I can see the changes. I've done the following so far.
Forked the Testcafe repo
npm linked the forked repo to my current project https://medium.com/#alexishevia/the-magic-behind-npm-link-d94dcb3a81af
changed the package.json file's main entry to src/index instead of lib/index
When I npm run dev in my project I hit this error (no problems including the actual npm installation of testcafe)
import { GeneralError } from './errors/runtime';
^
SyntaxError: Unexpected token {
at Module._compile (internal/modules/cjs/loader.js:718:23)
My assumption (likely the impetus of my problem) based on this error is that I need the "built" version of testcafe (via npm run build). Unfortunately, npm run build isn't a script available in the testcafe repo, and I can't figure out how to do it otherwise.
What I've tried:
running the available npm scripts
reading gulp documentation, hoping it was gulp based
I'm in high friction scenario here, which is usually a sign that I've missed a crucial detail and I'm not even close to the right path.
To build TestCafe, execute the gulp build command from the fork root directory. It will build TestCafe into the lib folder.
UPD: In addition, refer to the Contributing to TestCafe page, which contains all information you may need to start contributing to TestCafe: Code of Conduct, build/test instructions, and more.
Related
https://github.com/dremio/dremio-oss/blob/master/pom.xml
After I clone the project,I try to build the project, but some dependencies are not found .How to find these dependencies,such as
the project accquire calicte:4.0.0-20210722102535-bda216e83f-dremio,which can not find in mavencenter
Any help?
I tried building dremio-oss on Windows the other day and there were no problems with resolving dependencies. You should include more information from the build log. You can also try using the "-U" option to force checking remote repositories which is useful if your local repository cache is out of date. Your error message also doesn't make sense since the correct version for Calcite is this one: https://github.com/dremio/dremio-oss/blob/master/pom.xml#L46
I decided to add an ng-add schematic to my library, since there are additional setup steps when installing it past running npm/yarn install. This way, users will be able to run ng add #myorg/mylib and the schematics will run
I am having difficulty test running the schematic. Angular Guide only mentions how to test generate schematics, not add ones. The problem is that the schematic is supposed to run when I install the library, however ng add command always seems to install the repository version, and not the local one even if I link my library with yarn link
Thanks for your help.
Ok, I got an answer before I submitted the question.
Do yarn link mylibrary, and then ng add mylibrary. ng add doesn't require the library not to be installed, it will try to install, but fail gracefully if the library is already installed with a warning
Skipping installation: Package already installed
Your ng-add script probably contains context.addTask(new NodePackageInstallTask());. Since link already "installed" the library in your node_modules, this will fail. The solution is to comment this line out while you're developing, and reenable it before publishing.
following example in Tensorflow site;
i am trying to retrain inception model final layer in Ubuntu+python 2.7 environment.when running below command
$ bazel build /home/incept/tensorflow/tensorflow/examples/image_retraining:retrain
it gives an error.
ERROR: not a valid absolute pattern (absolute target patterns must start with exactly two slashes)
any suggestion to fix this? example mention try
$ bazel build tensorflow/examples/image_retraining:retrain
Just to summarize general TensorFlow build issue debugging (on Linux) in case other people end up here with similar issues:
Make sure you're in the directory you checked out. So if git clone made you a tensorflow directory, bazel commands should be run in that directory tree. It doesn't matter where in the tree if the build target is absolute (//tensorflow/...).
Run ./configure in the tensorflow directory. This fetches necessary dependencies in addition to allowing you to configure the build (you can yes "" | ./configure if you don't want to bother answering the questions and just want the defaults).
Make sure you have the latest version of Bazel and a compatible Java installation.
The git repository changes quite a bit. git pull will get you the latest (git checkout can get you any version you'd like).
Ok, be forewarned, I am SUPER noob when it comes to bower. I have a very sketchy basic understanding of what it even is and barely know how to do anything on it. So bear with me here. Also, I'm working on Windows here.
I installed node.js, and then used npm to install bower. After spending half my life trying to find the bower folder, if found it in
C:\Users\ME\AppData\Roaming\npm\node_modules\bower
However, I just installed Foundation via Bower and have NO idea where it installed the Foundation files. I assume from my Google searches that it's in the bower_components folder, but I have no idea where that is. I haven't moved it around or done anything abnormal, so I assume it should just be somewhere pretty standard, but I can't find it anywhere! Any pointers on where to look? I have looked this up online a bunch of times, but either this is super obvious so nobody has ever been noob enough to ask it or I'm just bad at Googling my life problems. Is there a command I can run to find out where this is?
It depends. If you are using -g flag when isntalling, it tells npm or bower to install packages globally. It meens you can use them in the whole system and not only for the one project. In this case they are installed into AppData folder, node_modules for npm and bower_components for bower.
On the other hand, if you don't use -g flag, you are installing packages only for the project which you are actually working on. It is simply the folder where you are when you run the install command. Then folders node_packages and bower_components are created in your actual folder and packages are placed into them.
If you install with -g flag, packages will be install globally. But when you download without -g flag, you can change bower package directory with .bowerrc file.
You should create .bowerrc file if not exist, and write this in file.
{
"directory" : "src/components"
}
I am new in Ubuntu/Linux and I've been working with java using the NetBeans IDE, so I don't have much experience with building c++ projects. But now I have to provide a proof of concept and I need to connect a C++ client with my ActiveMQ server. I downloaded The ActiveMQ-CPP API from this link, but I can't build/run it.
The download came with the files: Maklefile.am and Makefile.in. I searched it and I found that I need automake/autoconf to build it. I tried running ./configure but it says that it couldn't find such file or directory. I tried
sudo apt-get update
sudo apt-get install automake
sudo apt-get install autoconf
and a lot of other commands that I found on the Internet. None of then worked. I know that this question is really basic and it seems to be already answered somewhere else, but every attempt I've made failed. I think I'm missing something. I even tried the solution provided in the last message in this topic but it didn't work either.
Can anyone help me install autoconf/automake, or tell me how to use Makefile.am / Makefile.in to build the project I downloaded, or even suggest me some other way of building it?
Since you're open to other methods of building your project, I'm going to suggest CMake. It is a far better build system than autotools (at least from where I stand).
#CMakeLists.txt
project(MyProject CXX)
set_minimum_required(VERSION 2.8)
add_executable(foobar foo.cpp bar.cpp)
That example will build an executable called "foobar" by compiling and linking foo.cpp and bar.cpp. Put the above code in a file called CMakeLists.txt, then run the following commands:
cmake <path to project> #run in the folder you want to build in
make #this does the actual work
The really cool thing about CMake is that it generates a build system (Makefiles by default) but you can use it to generate project files for Eclipse, a Visual Studio solution, and a bunch of other things. If you want more information, I'd check out their documentation.
The "configure" script should be in your ActiveMQ-cpp source directory. From the Linux command line, you should be able to:
1) "cd" into your ActiveMQ* directory
2) "ls -l" to see the "configure" script
3) "./configure" to set things up for building the library\
4) "make" to actually build the library
This is mentioned in comments, but this particular point of confusion has been common for well over a decade and I think needs to be clarified as often as possible. You DO NOT need to have autoconf or automake installed to build a project that used those tools. The entire point of the autotools is to generate a build system that will build on a system using only the standard tools (make, a c compiler, sh, and few others.) Unfortunately, many developers release tarballs that do not build cleanly. If you unpack the tarball and it does not contain a configure script, or if the configure script is broken, that is a bug in the package. The solution is absolutely not to install autoconf/automake/libtool and try to produce a working configure script. The solution is to report the build error as a bug to the package maintainer.
The world would be a better place if Linux distributions stopped installing multiple versions of the autotools by default as less than .002% of the population needs those tools, and anyone who actually needs to have the tools should be capable of installing it themselves. Anyone incapable of acquiring and installing the tools has no business using them.